Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved c
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill PW.6.2_pw62 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of PW.6.2 Pw62?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-pw-6-2-pw62)More formats (shields.io, HTML) on the badges page.
---
name: "PW.6.2_pw62"
description: "Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved c"
category: "input-validation"
version: "1.1"
author: "cyberstrike-official"
tags:
- nist
- sp800-218
- ssdf
- pw-6-2
- pw
- secure-development
- task
tech_stack:
- any
cwe_ids:
- CWE-20
chains_with: []
prerequisites:
- Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security (PW.6)
severity_boost: {}
---
# PW.6.2 PW.6.2
> **Task of practice:** Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security (PW.6)
## High-Level Description
**Practice Group:** Produce Well-Secured Software (PW)
**Framework:** NIST SP 800-218 SSDF v1.1
Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations.
## What to Check
- [ ] Verify PW.6.2 PW.6.2 is integrated into SDLC
- [ ] Review CI/CD pipeline for PW.6.2 implementation
- [ ] Confirm automated tooling supports this practice
## How to Test
### Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.6.2 practice implementation.
### Step 2: Verify Tooling
```
# Check CI/CD pipeline configuration
# Verify security tools are integrated
# Example: Check for SAST/DAST in pipeline
grep -r "security\|scan\|sast\|dast" .github/workflows/ 2>/dev/null
grep -r "security\|scan" Jenkinsfile 2>/dev/null
```
### Step 3: Assess Developer Awareness
Verify development team understands and follows PW.6.2 PW.6.2 practice.
## Tools
| Tool | Purpose | Usage |
| ------------------- | ---------------------------------- | ---------------------------- |
| github-security-mcp | Check repository security settings | `github_security_*` tools |
| Manual Review | SDLC process review | Documentation and interviews |
## Remediation Guide
Implement PW.6.2 PW.6.2 in the software development lifecycle:
Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations.
## Risk Assessment
| Finding | Severity | Impact |
| ----------------------------- | -------- | -------------------------------------------------- |
| PW.6.2 PW.6.2 not implemented | Medium | Secure Development - Produce Well-Secured Software |
## CWE Categories
| CWE ID | Title |
| ------ | ------------------------- |
| CWE-20 | Improper Input Validation |
## References
- [NIST SP 800-218 SSDF v1.1](https://csrc.nist.gov/pubs/sp/800/218/final)
- [NIST SSDF Practices](https://csrc.nist.gov/projects/ssdf)
- [NIST OSCAL Content](https://github.com/usnistgov/oscal-content)
## Checklist
- [ ] Practice documented in SDLC policy
- [ ] Tooling configured and operational
- [ ] Development team trained
- [ ] Evidence of consistent application
- [ ] Periodic review scheduled
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!