OpenParable
Skip to content
← Back to skills

Create Source Code by Adhering to Secure Coding Practices (PW.5)_create-source-code-by-adhering-to-secure-coding-practices

Development

Create Source Code by Adhering to Secure Coding Practices (PW.5)_create-source-code-by-adhering-to-secure-coding-practices is an Agent Skill for development published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Decrease the number of security vulnerabilities in the software, and reduce costs by minimizing vulnerabilities introduced during source code creation

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-218_SSDF/PW_produce-well-secured-software/Create Source Code by Adhering to Secure Coding Practices (PW.5)_create-source-code-by-adhering-to-secure-coding-practices/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/create-source-code-by-adhering-to-secure-coding-practices-pw-5-create-source-code-by-adher-273391a0, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Create Source Code by Adhering to Secure Coding Practices (PW.5) Create Source Code by Adhering to Secure Coding Practices

High-Level Description

Practice Group: Produce Well-Secured Software (PW) Framework: NIST SP 800-218 SSDF v1.1

Decrease the number of security vulnerabilities in the software, and reduce costs by minimizing vulnerabilities introduced during source code creation that meet or exceed organization-defined vulnerability severity criteria.

What to Check

  • Verify Create Source Code by Adhering to Secure Coding Practices (PW.5) Create Source Code by Adhering to Secure Coding Practices is integrated into SDLC
  • Review CI/CD pipeline for Create Source Code by Adhering to Secure Coding Practices (PW.5) implementation
  • Confirm automated tooling supports this practice

How to Test

Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of Create Source Code by Adhering to Secure Coding Practices (PW.5) 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 Create Source Code by Adhering to Secure Coding Practices (PW.5) Create Source Code by Adhering to Secure Coding Practices practice.

Tools

ToolPurposeUsage
github-security-mcpCheck repository security settingsgithub_security_* tools
Manual ReviewSDLC process reviewDocumentation and interviews

Remediation Guide

Implement Create Source Code by Adhering to Secure Coding Practices (PW.5) Create Source Code by Adhering to Secure Coding Practices in the software development lifecycle:

Decrease the number of security vulnerabilities in the software, and reduce costs by minimizing vulnerabilities introduced during source code creation that meet or exceed organization-defined vulnerability severity criteria.

Risk Assessment

FindingSeverityImpact
Create Source Code by Adhering to Secure Coding Practices (PW.5) Create Source Code by Adhering to Secure Coding Practices not implementedMediumSecure Development - Produce Well-Secured Software

CWE Categories

CWE IDTitle
CWE-20Improper Input Validation

References

Checklist

  • Practice documented in SDLC policy
  • Tooling configured and operational
  • Development team trained
  • Evidence of consistent application
  • Periodic review scheduled