pw-1-1-pw11

Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.

Zur Installation springen

Repository: CyberStrikeus/CyberStrike
Letzte Quellaktivität: 22. April 2026 um 14:54
Erkannte Sprache von SKILL.md: Englisch
Sterne: 1.653
Forks: 254

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/CyberStrikeus/CyberStrike --skill pw-1-1-pw11

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

PW.1.1 PW.1.1

Task of practice: Design Software to Meet Security Requirements and Mitigate Security Risks (PW.1)

High-Level Description

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

Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.

What to Check

Verify PW.1.1 PW.1.1 is integrated into SDLC
Review CI/CD pipeline for PW.1.1 implementation
Confirm automated tooling supports this practice

How to Test

Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of PW.1.1 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.1.1 PW.1.1 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.1.1 PW.1.1 in the software development lifecycle:

Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.

Risk Assessment

Finding	Severity	Impact
PW.1.1 PW.1.1 not implemented	Medium	Secure Development - Produce Well-Secured Software

CWE Categories

CWE ID	Title
CWE-20	Improper Input Validation

References

Checklist

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

name	PW.1.1_pw11
description	Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.
category	input-validation
version	1.1
author	cyberstrike-official
tags	["nist","sp800-218","ssdf","pw-1-1","pw","secure-development","task"]
tech_stack	["any"]
cwe_ids	["CWE-20"]
chains_with

name	PW.1.1_pw11
description	Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.
category	input-validation
version	1.1
author	cyberstrike-official
tags	["nist","sp800-218","ssdf","pw-1-1","pw","secure-development","task"]
tech_stack	["any"]
cwe_ids	["CWE-20"]
chains_with

pw-1-1-pw11

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Mehr aus diesem Repository

PW.1.1 PW.1.1

High-Level Description

What to Check

How to Test

Step 1: Review SDLC Documentation

Step 2: Verify Tooling

Step 3: Assess Developer Awareness

Tools

Remediation Guide

Risk Assessment

CWE Categories

References

Checklist