System Classification(s): All Classifications; Compliance: MUST 5.4.5.C.01. Control [CID:828] Agencies MUST select controls from this manual to be included in the SSP based on the scope of the system with additional system specific controls being included as a result of the associated SRMP. Encryption Key Management requires specific consideration; refer to Chapter 17 – Cryptography. 5.4.5.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:829] Agencies SHOULD use the latest baseline of this manual when developing, and updating, their SSPs as part of the certification, accreditation and reaccreditation of their systems. 5.4.5.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:831] Agencies SHOULD include a Key Management Plan in the SSP. 5.5. Standard Operating Procedures Objective 5.5.1. Standard Operating Procedures (SOPs) ensure security procedures are followed in an appropriate and repeatable manner. Context Scope 5.5.2. This section relates to the development of security related SOPs. Information relating to other mandatory documentation can be found inSection 5.1 Documentation Fundamentals. Rationale & Controls 5.5.3. Development of SOPs 5.5.3.R.01. Rationale In order to ensure that personnel undertake their duties in an appropriate manner, with a minimum of confusion, it is important that the roles of ITSMs, system administrators and system users are covered by SOPs. Furthermore, taking steps to ensure that SOPs are consistent with SSPs will reduce the potential for confusion resulting from conflicts in policy and procedures. 5.5.3.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:844] Agencies SHOULD develop SOPs for each of the following roles: ITSM; system administrator; and system user. 5.5.4. ITSM SOPs 5.5.4.R.01. Rationale The ITSM SOPs are intended to cover the management and leadership of information security functions within the agency. 5.5.4.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:849] The following procedures SHOULD be documented in the ITSMs SOPs. Topic Procedures to be included Access control Authorising access rights to applications and data. Asset Musters Labelling, registering and mustering assets, including media. Audit logs Reviewing system audit trails and manual logs, particularly for privileged users. Configuration control Approving and releasing changes to the system software or configurations. Information security Detecting, reporting and managing potential information security incidents. incidents Establishing the cause of any information security incident, whether accidental or deliberate. Actions to be taken to recover and minimise the exposure from an information security incident. Additional actions to prevent reoccurrence. Data transfers Managing the review of media containing classified information that is to be transferred off-site. Managing the review of incoming media for malware or unapproved software. IT equipment Managing the disposal & destruction of unserviceable IT equipment and media. System Patching Advising and recommending system patches, updates and version changes based on security notices and related advisories. System integrity audit 48 Reviewing system user accounts, system parameters and access controls to ensure that the system is secure. Version_3.5__January-2022

Select target paragraph3

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