{"data":{"id":"SA-05","name":"System Documentation","family":"SA","family_name":"System and Services Acquisition","withdrawn":false,"description":"a. Obtain or develop administrator documentation for the system, system component, or system service that describes:\n1. Secure configuration, installation, and operation of the system, component, or service;\n2. Effective use and maintenance of security and privacy functions and mechanisms; and\n3. Known vulnerabilities regarding configuration and use of administrative or privileged functions;\nb. Obtain or develop user documentation for the system, system component, or system service that describes:\n1. User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;\n2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and\n3. User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;\nc. Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take [Assignment: organization-defined actions] in response; and\nd. Distribute documentation to [Assignment: organization-defined personnel or roles].","supplemental_guidance":"System artifacts and documentation created by the developer helps organizational personnel understand the implementation and operation of controls. Organizations consider establishing specific measures to determine the quality and completeness of the content provided. System documentation may be used to delineate roles, responsibilities, and expectations of the developer and organization, support the management of supply chain risk, incident response, and other functions. Personnel or roles that require documentation include system owners, system security officers, and system administrators. Attempts to obtain documentation include contacting manufacturers or suppliers and conducting web-based searches. The inability to obtain documentation may occur due to the age of the system or component or the lack of support from developers and contractors. When documentation cannot be obtained, organizations may need to recreate the documentation if it is essential to the implementation or operation of the controls. The protection provided for the documentation is commensurate with the security category or classification of the system. Documentation that addresses system vulnerabilities may require an increased level of protection. Secure operation of the system includes initially starting the system and resuming secure system operation after a lapse in system operation.","enhancements":[{"id":"SA-05(01)","name":"Functional Properties of Security Controls","withdrawn":true,"incorporated_into":["SA-04(01)"]},{"id":"SA-05(02)","name":"Security-relevant External System Interfaces","withdrawn":true,"incorporated_into":["SA-04(02)"]},{"id":"SA-05(03)","name":"High-level Design","withdrawn":true,"incorporated_into":["SA-04(02)"]},{"id":"SA-05(04)","name":"Low-level Design","withdrawn":true,"incorporated_into":["SA-04(02)"]},{"id":"SA-05(05)","name":"Source Code","withdrawn":true,"incorporated_into":["SA-04(02)"]}],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"SA-05","name":"System Documentation","description":"a. Obtain or develop administrator documentation for the system, system component, or system service that describes:\n1. Secure configuration, installation, and operation of the system, component, or service;\n2. Effective use and maintenance of security and privacy functions and mechanisms; and\n3. Known vulnerabilities regarding configuration and use of administrative or privileged functions;\nb. Obtain or develop user documentation for the system, system component, or system service that describes:\n1. User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;\n2. Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and\n3. User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;\nc. Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take [Assignment: organization-defined actions] in response; and\nd. Distribute documentation to [Assignment: organization-defined personnel or roles].","discussion":"System artifacts and documentation created by the developer helps organizational personnel understand the implementation and operation of controls. Organizations consider establishing specific measures to determine the quality and completeness of the content provided. System documentation may be used to delineate roles, responsibilities, and expectations of the developer and organization, support the management of supply chain risk, incident response, and other functions. Personnel or roles that require documentation include system owners, system security officers, and system administrators. Attempts to obtain documentation include contacting manufacturers or suppliers and conducting web-based searches. The inability to obtain documentation may occur due to the age of the system or component or the lack of support from developers and contractors. When documentation cannot be obtained, organizations may need to recreate the documentation if it is essential to the implementation or operation of the controls. The protection provided for the documentation is commensurate with the security category or classification of the system. Documentation that addresses system vulnerabilities may require an increased level of protection. Secure operation of the system includes initially starting the system and resuming secure system operation after a lapse in system operation.","related_controls":["CM-04","CM-06","CM-07","CM-08","PL-02","PL-04","PL-08","PS-02","SA-03","SA-04","SA-08","SA-09","SA-10","SA-11","SA-15","SA-16","SA-17","SI-12","SR-03"],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":false,"changes_from_rev4":"Adds \"or develop\" regarding documentation; adds privacy reference"}},"compliance_mappings":{"iso_27001_2022":["7.5","A.5.37"],"iso_27002_2022":["5.37"],"cobit_2019":["BAI08"],"pci_dss_v4":[],"nist_csf_2":["ID.AM-02","ID.RA-09"],"cis_controls_v8":[],"soc2_tsc":["CC6.1-POF1"],"finos_ccc":[],"iso_42001_2023":["A.6.2.3","A.6.2.7","A.8.2"],"iec_62443":[],"asd_e8":[],"nis2":[],"apra_cps_234":[],"mas_trm":[],"pra_op_resilience":[],"bsi_grundschutz":[],"anssi":["Hygiene.5","SecNumCloud.15.2"],"osfi_b13":["B-13.2.2"],"finma_circular":["IV.A(28)","IV.A(36)"],"gdpr":["Art.30(1)"],"dora":["Art.8(1)","Art.8(4)"],"bio2":["5.37"],"rbi_csf":["Annex1.6"],"fisc":[],"lgpd_bcb":[],"hkma_tme1":["TME1.3.4"],"mlps_2":["8.1.9.5"],"dnb_good_practice":[],"cra":["CRA.Info.4","CRA.Info.5","CRA.Info.8a","CRA.Info.8b","CRA.Info.8c","CRA.Info.8d","CRA.Info.8e","CRA.Info.8f"],"swift_cscf":[],"qatar_nia":["SD"],"uae_ia":["T10"],"bog_cisd":["CISD-SDLC"],"bcbs_239":["Principle 2"],"cpmi_pfmi":["PFMI.P17"],"eba_ict":["3.3.2"],"hipaa_sr":["§164.316(b)(1)","§164.316(b)(2)(ii)"],"iosco_cyber":["ID-1"],"nerc_cip":[],"nrc_73_54":[],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":[],"api_1164":[],"awia":[],"iaea_nss":[],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":[],"common_criteria":[],"isae_3402":["Clause 9"],"fca_sysc_13":["SYSC 13.6.5"],"fda_21_cfr_11":["§11.10(k)"],"fda_cyber":["SPDF-3","TR-1","TR-2","TR-3"],"hitrust_csf":[],"iso_27799":["12.1"],"lloyds_ms":[],"naic_ds":[],"nhs_dspt":[],"pra_ss1_23":["P3.1","P3.5"],"solvency_ii":["EIOPA-ICT-4.3"],"owasp_masvs_v2":[],"csa_ccm_v4":[],"csa_aicm":[],"ccss_v9":[],"mica":["Art.84(1)"],"basel_sco60":[],"bssc":[],"sec_custody_digital":[],"dpdpa":[]},"attack_techniques":[],"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: iso_27001_2022 7.5 added from NIST's SP 800-53 Rev 5 to ISO/IEC 27001:2022 crosswalk (OLIR entry 155), which OSA's mapping now takes as its base. 2026-10-03: nist_csf_2 ID.AM-02, ID.RA-09 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-001","SP-002","SP-011","SP-020"]}}