System Classification(s): All Classifications; Compliance: MUST 5.1.10.C.01. Control [CID:702] Agencies MUST ensure that every system is covered by a SSP. 5.1.11. Standard Operating Procedures (SOPs) 5.1.11.R.01. Rationale SOPs provide step-by-step guides to undertaking information security related tasks and processes. They provide assurance that tasks can be undertaken in a secure and repeatable manner, even by system users without strong technical knowledge of the system’s mechanics. Depending on the documentation framework chosen, some procedures common to multiple systems could be consolidated into a higher level SOP. 5.1.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:705] Agencies MUST ensure that Standard Operating Procedures (SOPs) are developed for systems. 5.1.12. Incident Response Plan (IRP) 5.1.12.R.01. Rationale The purpose of developing an IRP is to ensure that information security incidents are appropriately managed. In most situations the aim of the response will be to contain the incident and prevent the information security incident from escalating. The preservation of any evidence relating to the information security incident for criminal, forensic and process improvement purposes is also an important consideration. 5.1.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:708] Agencies MUST develop an Incident Response Plan and supporting procedures. 5.1.12.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:709] Agency personnel MUST be trained in and periodically exercise the Incident Response Plan. 5.1.13. Emergency Procedures (EP) 5.1.13.R.01. Rationale Classified information and systems are secured if a building emergency or evacuation is required. 5.1.13.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:712] Agencies SHOULD document procedures relating to securing classified information and systems when required to evacuate a facility in the event of an emergency. 5.1.14. Developing content 5.1.14.R.01. Rationale Ensuring personnel developing information security documentation are sufficiently knowledgeable of information security issues and business requirements will assist in achieving the most useful and accurate set of documentation. 5.1.14.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:715] Agencies SHOULD ensure that information security documentation is developed by personnel with a good understanding of policy requirements, the subject matter, essential processes and the agency’s business and operations 5.1.15. Documentation content 5.1.15.R.01. Rationale As the SRMP, Systems Architecture, SSP, SOPs and IRP are developed as a documentation suite for a system it is essential that they are logically connected and consistent within themselves and with other agency systems. Furthermore, each documentation suite developed for a system will need to be consistent with the agency’s overarching SecPol. 5.1.15.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:718] Agencies SHOULD ensure that their SRMP, Systems Architecture, SSP, SOPs and IRP are logically connected and consistent for each system, other agency systems and with the agency’s SecPol. 5.1.16. Documentation framework 5.1.16.R.01. Rationale The implementation of an overarching information security document framework ensures that all documentation is accounted for, complete and maintained appropriately. Furthermore, it can be used to describe linkages between documents, especially when higher level documents are used to avoid repetition of information in lower level documents. 5.1.16.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:721] Agencies SHOULD create and maintain an overarching document describing the agency’s documentation framework, including a complete listing of all information security documentation that shows a document hierarchy and defines how each document is related to the other. 5.1.16.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:722] Where an agency lacks an existing, well-defined documentation framework, they SHOULD use the document names defined in this manual. 5.1.17. Documentation Consistency 5.1.17.R.01. Rationale Consistency in approach, terminology and documentation simplifies the use and interpretation of documentation for different systems and agencies. 43 Version_3.5__January-2022

Select target paragraph3

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