Skip to main content
CMDashCybersecurity Maturity Dashboard
Protect (PR)

PR.IP-2 System development life cycle managed

NIST Cybersecurity Framework (1.1, legacy) · 1.1

What the standard requires

A System Development Life Cycle to manage systems is implemented

Quoted verbatim from NIST Cybersecurity Framework (CSF) 1.1, which is in the public domain.

Maps to 5 controls in 5 other frameworks

FrameworkControl
GDPRArt.25 Data protection by design and by default
ISO/IEC 27001:2022A.8.25 Secure development life cycle
NIST Cybersecurity Framework 2.0PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
PCI DSS v4.0.16.2 Bespoke and custom software developed securely
TISAX (VDA ISA v6)5.2.1 Secure development lifecycle is established

Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.

Integrations that carry evidence for this family

Okta
MFA & identity coverage

These connectors produce data relevant to NIST Cybersecurity Framework (1.1, legacy)’s Protect (PR) family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.

Track PR.IP-2 with evidence behind it

In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.

Start free trialAll NIST Cybersecurity Framework (1.1, legacy) controls
PR.IP-2 System development life cycle managed — NIST Cybersecurity Framework (1.1, legacy) | CMDash