OpenParable
Skip to content
← Back to skills

SA-18(1)_multiple-phases-of-system-development-life-cycle

Productivity

SA-18(1)_multiple-phases-of-system-development-life-cycle is an Agent Skill for productivity published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Multiple Phases of System Development Life Cycle

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-53_rev5/SA_system-and-services-acquisition/SA-18(1)_multiple-phases-of-system-development-life-cycle/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sa-18-1-multiple-phases-of-system-development-life-cycle, 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.

SA-18(1) Multiple Phases of System Development Life Cycle

Enhancement of: SA-18

High-Level Description

Family: System and Services Acquisition (SA) Framework: NIST SP 800-53 Rev 5

No description available.

What to Check

  • Verify SA-18(1) Multiple Phases of System Development Life Cycle is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for SA-18(1)
  • Verify enhancement builds upon base control SA-18

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SA-18(1) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

ToolPurposeUsage
Manual ReviewDocumentation and interview-basedN/A

Remediation Guide

Control Statement

Refer to NIST SP 800-53 Rev 5 for the full control statement.

Implementation Guidance

Implement this control per organizational risk assessment and system categorization.

Risk Assessment

FindingSeverityImpact
SA-18(1) Multiple Phases of System Development Life Cycle not implementedMediumSystem and Services Acquisition
SA-18(1) partially implementedLowIncomplete System and Services Acquisition

CWE Categories

CWE IDTitle
CWE-16Configuration

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (none) reviewed