unified
UC-CONFIG-04 — Build security and privacy into software design and upkeep
Engineer security and data-protection requirements into systems and software from design onward, applying secure coding standards, pre-release security testing, and privacy-preserving defaults such as data minimization and pseudonymization. Maintain software after release by remediating identified vulnerabilities and applying security patches within risk-based timeframes. Replace or remove software that is unsupported or no longer justified by risk.
Record JSON · Open in map · Data retrieval guide
Catalog revision: 24028ffcfc2b295fa1b08ee6caa84b765f0731b321496bf4f548c49ad2177028. A connection does not establish full coverage.
Attributes
- domain
- Secure Configuration & Change Management
- type
- preventive
- category
- technical
Details
- unified_id
- UC-CONFIG-04
- title
- Build security and privacy into software design and upkeep
- statement
- Engineer security and data-protection requirements into systems and software from design onward, applying secure coding standards, pre-release security testing, and privacy-preserving defaults such as data minimization and pseudonymization. Maintain software after release by remediating identified vulnerabilities and applying security patches within risk-based timeframes. Replace or remove software that is unsupported or no longer justified by risk.
- domain
- Secure Configuration & Change Management
- control_type
- preventive
- control_category
- technical
- members
- framework
- nist-csf-2
- control_id
- PR.PS-02
- coverage
- full
- relationship
- superset_of
- framework
- gdpr
- control_id
- GDPR-Art25
- coverage
- partial
- delta
- Art.25(2) data-protection-by-default applies organization-wide beyond software design; this control covers the by-design engineering arm
- relationship
- intersects_with
- framework
- pci-dss
- control_id
- PCI-Req6
- coverage
- partial
- delta
- also requires protections for public-facing web applications
- relationship
- intersects_with
- guidance
Source
No record-specific source URL is provided.
Connections
- UC-CONFIG-04 — Build security and privacy into software design and upkeep maps_to PR.PS-02 — Platform Security: Software is maintained, replaced, and removed commensurate with risk
- framework
- nist-csf-2
- control_id
- PR.PS-02
- coverage
- full
- relationship
- superset_of
- delta
- Not provided
- source_version
- 2.0
- provenance
- mapper
- coworkcanvas-compliance-graph
- reviewDate
- 2026-09-07
- direction
- canonical_to_source
- defaultConfidence
- medium
- defaultStatus
- active
- note
- Each member is a documented relationship claim from the canonical unified control to a source control or guidance proposition. relationship: equal|superset_of (full) / intersects_with|subset_of (partial) / informs (guidance). confidence 'medium' = single-mapper, documented, not yet externally corroborated. source_version is the member framework's edition from the standard version register.
- UC-CONFIG-04 — Build security and privacy into software design and upkeep maps_to GDPR-Art25 — Data protection by design and by default
- framework
- gdpr
- control_id
- GDPR-Art25
- coverage
- partial
- delta
- Art.25(2) data-protection-by-default applies organization-wide beyond software design; this control covers the by-design engineering arm
- relationship
- intersects_with
- source_version
- Regulation (EU) 2016/679
- provenance
- mapper
- coworkcanvas-compliance-graph
- reviewDate
- 2026-09-07
- direction
- canonical_to_source
- defaultConfidence
- medium
- defaultStatus
- active
- note
- Each member is a documented relationship claim from the canonical unified control to a source control or guidance proposition. relationship: equal|superset_of (full) / intersects_with|subset_of (partial) / informs (guidance). confidence 'medium' = single-mapper, documented, not yet externally corroborated. source_version is the member framework's edition from the standard version register.
- Secure Development & Release Security Gate operates UC-CONFIG-04 — Build security and privacy into software design and upkeep
- UC-CONFIG-04 — Build security and privacy into software design and upkeep mitigates Inadequate vulnerability scanning and pre-release testing
- strength
- primary
- rationale
- Pre-release security testing directly mitigates releasing software with undiscovered exploitable defects.
- Technical Security Testing & Pentest Engagement tests UC-CONFIG-04 — Build security and privacy into software design and upkeep
- UC-CONFIG-04 — Build security and privacy into software design and upkeep mitigates Applications running with excessive privilege / insecure design
- strength
- primary
- rationale
- Engineering security from design onward with secure-coding standards is the secure-by-design defense against insecurely designed, over-privileged applications.
- UC-CONFIG-04 — Build security and privacy into software design and upkeep maps_to PCI-Req6 — Develop and maintain secure systems and software
- framework
- pci-dss
- control_id
- PCI-Req6
- coverage
- partial
- delta
- also requires protections for public-facing web applications
- relationship
- intersects_with
- source_version
- v4.0.1
- provenance
- mapper
- coworkcanvas-compliance-graph
- reviewDate
- 2026-09-07
- direction
- canonical_to_source
- defaultConfidence
- medium
- defaultStatus
- active
- note
- Each member is a documented relationship claim from the canonical unified control to a source control or guidance proposition. relationship: equal|superset_of (full) / intersects_with|subset_of (partial) / informs (guidance). confidence 'medium' = single-mapper, documented, not yet externally corroborated. source_version is the member framework's edition from the standard version register.
- UC-CONFIG-04 — Build security and privacy into software design and upkeep mitigates Exploitation of known, unpatched vulnerabilities
- strength
- primary
- rationale
- Applying security patches within risk-based timeframes and replacing unsupported software directly mitigates exploitation of known unpatched flaws.
- UC-CONFIG-04 — Build security and privacy into software design and upkeep mitigates Loss of system maintainability
- strength
- related
- rationale
- Patching and replacing unsupported software keeps systems current and patchable, contributing to maintainability; maintenance support/tooling is the operative control.