4.3.19. Implementing controls 4.3.19.R.01. Rationale System testing is most effective on working systems. Desk checks have limited effectiveness in these situations. 4.3.19.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:576] Prior to undertaking any system testing in support of the certification process, the system owner MUST implement the controls for the system. 4.3.20. Audit (second stage) 4.3.20.R.01. Rationale The purpose of the second stage of the audit is to determine whether the controls, as approved by the system owner and reviewed during the first stage of the audit, have been implemented correctly and are operating effectively. 4.3.20.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:579] The implementation of controls MUST be assessed to determine whether they have been implemented correctly and are operating effectively. 4.3.20.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:580] The auditor MUST ensure that, where applicable, a physical security certification has been awarded by an appropriate physical security certification authority. 4.3.20.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:581] The physical security certification SHOULD be less than three (3) years old at the time of the audit. 4.3.21. Report of compliance 4.3.21.R.01. Rationale The report of compliance assists the certification authority in conducting a residual security risk assessment to assess the residual security risk relating to the operation of a system following the audit and any remediation activities the system owner may have undertaken. 4.3.21.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:584] The auditor MUST produce a report of compliance for the certification authority outlining areas of non-compliance for a system and any suggested remediation actions. 4.4. Accreditation Framework Objective 4.4.1. Accreditation is the formal authority for a system to operate, and an important element in fundamental information system governance. Accreditation requires risk identification and assessment, selection and implementation of baseline and other appropriate controls and the recognition and acceptance of residual risks relating to the operation of a system including any outsourced services such as Telecommunications or Cloud. Accreditation relies on the completion of system certification procedures. Context Scope 4.4.2. This section covers information on the accreditation framework for systems. 4.4.3. All types of government held information are covered, including Official Information and information subject to privacy requirements. Rationale & Controls 4.4.4. Accreditation framework 4.4.4.R.01. Rationale The development of an accreditation framework within the agency will ensure that accreditation activities are conducted in a repeatable and consistent manner across the agency and that consistency across government systems is maintained. This requirement is a fundamental part of a robust governance model and provides a sound process to demonstrate good governance of information systems. 4.4.4.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:595] Agencies MUST develop an accreditation framework for their agency. 4.4.5. Accreditation 4.4.5.R.01. Rationale Accreditation ensures that either sufficient security measures have been put in place to protect information that is processed, stored or communicated by the system or that deficiencies in such measures have been identified, assessed and acknowledged by an appropriate authority. As such, when systems are awarded accreditation the Accreditation Authority accepts that the residual security risks relating to the system are appropriate for the information that it processes, stores or communicates. 4.4.5.R.02. Rationale Once systems have been accredited, conducting on-going monitoring activities will assist in assessing changes to its environment and operation and to determine the implications for the security risk profile and accreditation status of the system. 4.4.5.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:599] Agencies MUST ensure that each of their systems is awarded accreditation. 4.4.5.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:600] Agencies MUST ensure that all systems are awarded accreditation before they are used operationally. 37 Version_3.5__January-2022

Select target paragraph3

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