5.1.17.R.02. Rationale Factors which should be taken into account when determining the classification of systems documentation include: Highest classification of information stored, processed or communicated over that system; Sensitivity including existence of the facility; Inclusion of vulnerability information, security mechanisms or special processing capability in the systems documentation; Potential data aggregation; Risk and threat levels; and Scope and use of the system. 5.1.17.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:726] Where an agency uses alternative documentation names to those defined within this manual for their information security documentation they SHOULD convert the documentation names to those used in this manual. 5.1.18. Documentation Classification 5.1.18.R.01. Rationale Systems documentation will usually reflect the importance or sensitivity of particular systems. 5.1.18.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:729] Agencies MUST ensure that their SecPol, SRMP, SSP, SOPs and IRP are appropriately classified. 5.1.19. Outsourcing development of content 5.1.19.R.01. Rationale Agencies outsourcing the development of information security documentation need to be aware of the contents of the documentation produced. As such, they will still need to review and control the documentation contents to make sure it is appropriate and meets their requirements. 5.1.19.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:732] When information security documentation development is outsourced, agencies SHOULD: review the documents for suitability; retain control over the content; and ensure that all policy requirements are met. 5.1.20. Obtaining formal sign-off 5.1.20.R.01. Rationale Without appropriate sign-off of information security documentation within an agency, the security personnel will have a reduced ability to ensure appropriate security procedures are selected and implemented. Having sign-off at an appropriate level assists in reducing this security risk as well as ensuring that senior management is aware of information security issues and security risks to the agency’s business. 5.1.20.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:735] All information security documentation SHOULD be formally approved and signed off by a person with an appropriate level of seniority and authority. 5.1.20.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:736] Agencies SHOULD ensure that: all high-level information security documentation is approved by the CISO and the agency head or their delegate; and all system-specific documents are reviewed by the ITSM and approved by the system owner. 5.1.21. Documentation Maintenance 5.1.21.R.01. Rationale The threat environment and agencies’ businesses are dynamic. If an agency fails to keep their information security documentation up to date to reflect the changing environment, they do not have a means of ascertaining that their security measures and processes continue to be effective. 5.1.21.R.02. Rationale Changes to risk and technology may dictate a reprioritisation of resources in order to maximise the effectiveness of security measures and processes. 5.1.21.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:767] Agencies SHOULD develop a regular schedule for reviewing all information security documentation. 5.1.21.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:768] Agencies SHOULD ensure that information security documentation is reviewed: at least annually; or in response to significant changes in the environment, business or system; and with the date of the most recent review being recorded on each document. 5.2. Information Security Policies 44 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents