their specific system. Information security documentation is detailed in Chapter 5 - Information Security documentation. Refer also to Chapter 4
- System Certification and Accreditation.
3.4.12.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:449]
System owners MUST ensure the development, maintenance and implementation of complete, accurate and up to date Information Security
documentation for systems under their ownership. Such actions MUST be documented.
3.4.12.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:450]
System Owners MUST involve the ITSM in the redevelopment and updates of the Information Security documentation.
3.5. System Users
Objective
3.5.1.
System users comply with information security policies and procedures within their agency.
Context
Scope
3.5.2.
This section covers the role that system users undertake with respect to information security.
Types of system users
3.5.3.
This section covers responsibilities for all system users i.e. users with general access (general users), and users with privileged access (privileged
users).
Rationale & Controls
3.5.4.
Responsibilities of system users
3.5.4.R.01.
Rationale
If agencies fail to develop and maintain a security culture where system users are complying with relevant security policies and procedures for
the systems they are using, there is an increased security risk of a system user unwittingly assisting with an attack against a system.
3.5.4.R.02.
Rationale
Security policies, procedures and mechanisms aim to cover all situations that may arise within an agency. However there may be legitimate
reasons for a system user to bypass security policies, procedures or mechanisms. If this is the case, the system user MUST seek formal
authorisations from the CISO or the ITSM (if this authority has been specifically delegated to the ITSM) before any actions are undertaken.
3.5.4.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:466]
All system users MUST comply with the relevant security policies and procedures for the systems they use.
3.5.4.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:467]
All system users MUST:
protect account authenticators at the same classification of the system it secures;
not share authenticators for accounts without approval;
be responsible for all actions under their accounts; and
use their access to only perform authorised tasks and functions.
3.5.4.C.03.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:468]
System users that need to bypass security policies, procedures or mechanisms for any reason MUST seek formal authorisation from the CISO or
the ITSM if this authority has been specifically delegated to the ITSM.
4. System Certification and Accreditation
4.1. The Certification and Accreditation Process
Objective
4.1.1.
Executives and Security Practitioners understand and enforce the use of the Certification and Accreditation (C&A) process and its role in information
security governance and assurance.
Context
Scope
4.1.2.
This section provides a short, high-level description of the C&A process.
4.1.3.
This section must be read in conjunction with the Roles and Responsibilities described in Chapter 3. Subsequent sections of this chapter describe
elements of the C&A process in more detail.
The Process
4.1.4.
Certification and Accreditation is a fundamental governance and assurance process, designed to provide the Board, Chief Executive and senior
executives confidence that information and its associated technology are well-managed, that risks are properly identified and mitigated and that
governance responsibilities can demonstrably be met. It is essential for credible and effective information assurance governance.
4.1.5.
28
C&A has two important stages where certification must be completed before accreditation can take place. It is based on an assessment of risk, the
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents