Incident Response Plan IRP 5.1.12 Emergency Procedures EP 5.1.13 Independent Assurance reports for - 5.8 externally provided services PSR references 5.1.6. Additional information on third party providers is provided in the PSR. Reference PSR Mandatory Requirements Title GOV4, GOV5, INFOSEC1, INFOSEC2, PERSEC1, PERSEC2, PERSEC3 and PERSEC4 Source http://www.protectivesecurity.govt.nz https://www.protectivesecurity.govt.nz/governance/mandatory-requirements-2/ https://www.protectivesecurity.govt.nz/information-security/mandatoryrequirements-2/ https://www.protectivesecurity.govt.nz/personnel-security/mandatoryrequirements/ PSR content Management protocol for information security https://www.protectivesecurity.govt.nz/information-security/management- protocols Management protocol for personnel security protocol/ https://www.protectivesecurity.govt.nz/personnel-security/management-protocolfor-personnel-security/ PSR requirements Supply chain security https://www.protectivesecurity.govt.nz/governance/supply-chain-security/ Outsourcing, Offshoring and supply chains Outsourced ICT facilities Cloud Computing https://www.protectivesecurity.govt.nz/information-security/managing-specificscenarios/outsourcing-offshoring-and-supply-chains/ https://www.protectivesecurity.govt.nz/physical-security/specific- sections Managing specific scenarios scenarios/physical-security-for-ict/outsourced-ict-facilities/ https://www.protectivesecurity.govt.nz/information-security/managing-specificscenarios/cloud-computing/ Rationale & Controls 5.1.7. Information Security Policy (SecPol) 5.1.7.R.01. Rationale The SecPol is an essential part of information security documentation as it outlines the high-level policy objectives. The SecPol can form part of the overall agency security policy. 5.1.7.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:692] Agencies MUST have a SecPol for their agency. The SecPol is usually sponsored by the Chief Executive and managed by the CISO or Chief Information Officer (CIO). The ITSM should be the custodian of the SecPol. The SecPol should include an acceptable use policy for any agency technology equipment, systems, resources and data. 5.1.8. Systems Architecture 5.1.8.R.01. Rationale The systems architecture illustrates the design of the system (including any outsourced services), consistency with the SecPol and provides the basis for the Security Risk Management Plan (SRMP). 5.1.8.R.02. Rationale In this context Systems Architecture includes Security Architecture. 5.1.8.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:696] All systems MUST have a documented Systems Architecture. 5.1.9. Security Risk Management Plan (SRMP) 5.1.9.R.01. Rationale The SRMP is considered to be a good practice approach to identifying and reducing identified security risks. Depending on the documentation framework chosen, multiple systems can refer to, or build upon, a single SRMP. 5.1.9.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:699] Agencies MUST ensure that every system is covered by a Security Risk Management Plan, which includes identification ofrisk owners. 5.1.10. System Security Plan (SSP) 5.1.10.R.01. Rationale The SSP describes the implementation and operation of controls within the system derived from the NZISM and the SRMP. Depending on the documentation framework chosen, some details common to multiple systems can be consolidated in a higher level SSP. 42 Version_3.5__January-2022

Select target paragraph3

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