Checking the integrity of system software. Testing access controls. System maintenance Managing the ongoing security and functionality of system software, including: maintaining awareness of current software vulnerabilities, testing and applying software patches/updates/signatures, and applying appropriate hardening techniques. User account management 5.5.5. Authorising new system users. System Administrator SOPs 5.5.5.R.01. Rationale The system administrator SOPs focus on the administrative activities related to system operations. 5.5.5.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:865] The following procedures SHOULD be documented in the system administrator’s SOPs. Topic Procedures to be included Access control Implementing access rights to applications and data. Configuration control Implementing changes to the system software or configurations. System backup and recovery Backing up data, including audit logs. Securing backup tapes. Recovering from system failures. User account management Adding and removing system users. Setting system user privileges. Cleaning up directories and files when a system user departs or changes roles. Incident response Detecting, reporting and managing potential information security incidents. Establishing the cause of any information security incident, whether accidental or deliberate. Actions to be taken to recover and minimise the exposure from information security incident. Additional actions to prevent reoccurrence. 5.5.6. System User SOPs 5.5.6.R.01. Rationale The system user SOPs focus on day to day activities that system users need to be made aware of, and comply with, when using systems. 5.5.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:884] The following procedures SHOULD be documented in the system user’s SOPs. 5.5.7. Topic Procedures to be included Acceptable Use Acceptable uses of the system(s). End of day How to secure systems at the end of the day. Information security incidents What to do in the case of a suspected or actual information security incident. Media control Procedures for handling and using media. Passwords Choosing and protecting passwords. Temporary absence How to secure systems when temporarily absent. Agreement to abide by SOPs 5.5.7.R.01. Rationale When SOPs are produced the intended audience should be made aware of their existence and acknowledge that they have read, understood and agree to abide by their contents. 5.5.7.C.01. 49 ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:889] Version_3.5__January-2022

Select target paragraph3

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