The policy framework

Security governance (GOV)

Ensure effective oversight and management of all protective security areas

Managing security risks proportionately and effectively enables organisations to protect people, information and assets. To successfully manage security risks organisations must ensure security is part of their organisational culture, practices and operational plans.

The PSR contains eight governance requirements which work together to ensure effective oversight and management of all security areas.

PSR Policy Framework — GOV

This section provides a high-level overview of the PSR security governance mandatory requirements. To understand, implement, and comply with the PSR security governance mandatory requirements, please refer to the following documents:

GOV 1

Establish and maintain the right governance

Establish and maintain a governance structure that ensures the successful leadership and oversight of protective security risk. Appoint members of the senior team as:

  • Chief Security Officer (CSO), responsible for your organisation’s overall protective security policy and oversight of protective security practices.
  • Chief Information Security Officer (CISO), responsible for your organisation’s information security.

To implement protective security requirements, your organisation must clearly:

  • identify your security governance structure
  • define who is responsible for security governance.

Develop a governance structure that enables you to effectively identify and manage security risks.

Your organisation head is responsible for reviewing and endorsing your proposed security risk management structures, assurance mechanisms, and resource allocations.

GOV 1 includes the following requirements:

GOV 1.1 Ensure executive commitment and oversight

GOV 1.1 covers the Organisation head’s key accountabilities and responsibilities for establishing and maintaining a secure environment that protects its people, information, and assets. This includes ensuring effective security governance, leadership and management, risk management, planning, and performance management.

  • Overall security accountability rests with the Organisation head
  • The Organisation head may delegate authority
  • Establish effective security governance oversight
  • Leaders promote and sponsor protective security

GOV 1.2 Assign functional security responsibilities

GOV 1.2 covers requirements for establishing an effective security management function. This includes requirements when considering appointing a Virtual CISO. Also refer to Security Governance Appendix A: Key protective security roles and responsibilities for more information.

  • Appoint a Chief Security Officer (CSO)
  • Appoint a Chief Information Security Officer (CISO)
  • Ensure functional management and governance responsibility
  • Ensure security management is active and visible
  • Convene a Security Reference Group (SRG) when appropriate.

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 1 mandatory requirement.

Guidance and resources

GOV 2

Take a risk-based approach

Adopt a risk management approach that covers every area of protective security across your organisation, in accordance with the New Zealand standard ISO 31000:2018 Risk Management – Guidelines.

Develop and maintain security policies and plans that meet your organisation’s specific business needs. Make sure you address security requirements in all areas: governance, information, personnel, and physical.

To successfully manage security risks, organisations must:

  • Identify, assess, and manage security risks, and
  • Formulate security plans to address those risks, and
  • Clearly define and articulate security policies, processes, and procedures that establish the expectations and approaches it will use to achieve security.

GOV 2 includes the following requirements:

GOV 2.1 Identify, assess, and manage security risks

GOV 2.1 covers requirements for security risk management including threat assessment and the recommended use of business impact levels (BILs) to help determine the impacts of risks. Also refer to Security Governance Appendix B: Business Impact Levels (BILs) for more information.

  • Adopt an appropriate risk management approach
  • Identify and assess protective security risks
  • Consider risk measures when working or co-locating with others
  • Manage your security risks effectively

GOV 2.2 Formulate security plans

GOV 2.2 covers requirements for security planning to effectively address your risks.

  • Ensure security plans addresses key risks
  • Regularly review, update, and phase security actions

GOV 2.3 Define and articulate security policies, processes, and procedures

GOV 2.3 covers requirements for establishing effective security policies, processes, and procedures across all security domains.

  • Develop security policies
  • Define security processes, procedures, and guidance
  • Review your security policies and processes

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 2 mandatory requirement.

Guidance and resources

GOV 3

Prepare for business continuity

Maintain a business continuity management programme, so that your organisation’s critical functions can continue to the fullest extent possible during a disruption. Ensure you plan for continuity of the resources that support your critical functions.

Business continuity is the capability of an organisation to continue delivery of products or services within acceptable timeframes, and at acceptable capacity following a disruptive event.

Causes of disruptions include natural events such as earthquakes or severe weather, loss of a key resource such as a power failure, technological failure, or supply chain disruption, as well as security threats such as sabotage, espionage, or cyber-attacks. Disruptions can occur at any time, for any reason, and their impact varies.

The International Standards Organisation (ISO) 22301 sets the standard for business continuity management (BCM).
An organisation must maintain a BCM programme to ensure it is effective and secure during a disruptive event. It must also consider how it will maintain protective security during a business continuity event and build effective security measures into its business continuity programme.

GOV 3 includes the following requirements:

GOV 3.1 Set the scope of the business continuity programme

GOV 3.1 covers requirements for establishing an appropriate business continuity programme.

  • Develop a policy for managing business continuity
  • Assign responsibility for business continuity

GOV 3.2 Identify critical functions and their requirements

GOV 3.2 covers requirements for understanding the critical functions in the organisation and their requirements for continuity during a disruptive event.

  • Identify critical functions
  • Conduct a business impact analysis

GOV 3.3 Develop solutions and plans for maintaining critical functions

GOV 3.3 covers requirements for ensuring that you have effective solutions, plans, and resources for maintaining your critical functions during a disruptive event.

  • Develop solutions
  • Document business continuity planning and procedures
  • Establish teams to manage business continuity in a disruption

GOV 3.4 Monitor the level of preparedness for a disruptive event

GOV 3.4 covers requirements for educating your people and validating your business continuity plans to confirm you are prepared for disruptions. This includes information on the different types of validations you may run (discussion exercise, scenario exercise, simulation exercise, live exercise, or testing of technology, equipment or procedures.

  • Educate people on your business continuity arrangements
  • Run exercises to validate business continuity plan and prepare for disruptions

GOV 3.5 Review and maintain the business continuity programme

GOV 3.5 covers requirements for regularly reviewing and maintaining your business continuity programme.

  • Review plans regularly to ensure effectiveness and continual improvement
  • Maintain your business continuity programme. 

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 3 mandatory requirement.

Guidance and resources

GOV 4

Build security awareness

Provide regular information, security awareness training, and support for everyone in your organisation, so they can meet the Protective Security Requirements and uphold your organisation’s security policies.

Building security awareness (including through training) helps an organisation to create a strong security culture that protects people, information, and assets.

An organisation must build security awareness to ensure that its people understand their security obligations, are aware of security risks, and follow security procedures.

GOV 4 includes the following requirements:

GOV 4.1 Establish a security awareness and training programme

GOV 4.1 covers requirements for establishing a security awareness and training programme including who to train, the scope of the programme, and how to ensure that the training programme is effective.

  • Set the scope of your security awareness and training programme
  • Set security awareness programme goals

GOV 4.2 Implement security awareness training

GOV 4.2 covers requirements for conducting security awareness training and the minimum topics for coverage.

  • Ensure security awareness is an ongoing and regular part of operations
  • Provide additional training for people in emergency, safety, or security roles
  • Train personnel on how to protect assets
  • Provide guidance on upholding legislation for protecting official information
  • Train personnel to report security concerns

GOV 4.3 Build a strong security culture

GOV 4.3 covers requirements for building and supporting a strong security culture.

  • Communicate effectively to enhance your security culture
  • Monitor training effectiveness
  • Monitor security behaviour and culture
  • Manage poor security behaviour effectively.

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 4 mandatory requirement.

Guidance and resources

GOV 5

Manage risks when working with others

Identify and manage the risks to your people, information, and assets before you begin working with others who may become part of your supply chain.

The PSR applies as much to service providers and outsourced services as it does to your internal operations. Organisations rely on suppliers to deliver products, systems, and services. This includes your partners, cooperating organisations, and customers. These suppliers broaden the risks the organisation is exposed to. Suppliers can be a weak point in an organisation’s security defences when they are not managed well.

An organisation must consider adopting twelve principles of supply chain security to manage protective security risk of its suppliers. 

GOV 5 includes the following requirements:

GOV 5.1 Understand the risks from your supply chain

Threats from an organisation’s supply chain come in many forms – inadequate security of their systems, a malicious insider working within, or undertake fraud or malicious acts of their own. Organisations must assess the risks its supply chain poses to its operation.

  • Principle 1: Understand what needs to be protected and why
  • Principle 2: Know who your suppliers are and understand their security measures
  • Principle 3: Understand the security risks posed by your supply chain

GOV 5.2 Establish effective control and oversight of your supply chain

Organisations must set and communicate its security requirements across the supply chain lifecycle and undertake effective due diligence before procuring or contracting new suppliers or establishing new partnerships. This requires mandated government organisations to follow New Zealand Government Rules for Procurement (including Rule 44 – Reasons to exclude a supplier).

  • Principle 4: Communicate your view of security needs to your suppliers
  • Principle 5: Set and communication minimum security requirements for your suppliers
  • Principle 6: Build security considerations in contracting process and require suppliers to do the same
  • Principle 7: Meet your own security responsibilities as a consumer
  • Principle 8: Raise awareness of security within your supply chain
  • Principle 9: Provide support for security incidents

GOV 5.3 Check you supply chain arrangements

Organisations must ensure that their supply chain is meeting its security requirements and should measure its security performance.

  • Principle 10: Build assurance activities into supply chain management

GOV 5.4 Continuous improvement

As security threats and risks are constantly changing, it is good practice to build continuous improvement processes within supply chain management processes.

  • Principle 11: Encourage the continuous improvement of security within your supply chain
  • Principle 12: Build trust with suppliers.

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 5 mandatory requirement.

Guidance and resources

GOV 6

Manage security incidents

Make sure every security incident is identified, reported, responded to, investigated, and recovered from as quickly as possible. Ensure any appropriate corrective action is taken.

A security incident is an event caused by an individual or group that has or could have resulted in loss or harm to an organisation’s assets, information or people, or an action that breaches the organisation’s security procedures. 

This may include:

  • an attack or attempted attack against a computer or network
  • an attempt or approach from anybody seeking unauthorised access to organisational resources, or
  • any other occurrence that results, or may result, in negative consequences for the security of the organisation, New Zealand government, its institutions, or programmes. 

Incident management is the process of identifying, recording, analysing, reporting, investigating, acting upon, and learning from incidents. Security investigations establish the cause and extent of an incident that has, or could have, compromised your organisation or the New Zealand Government.  The process of investigating and reporting security incidents also helps an organisation understand its vulnerabilities and reduce the risk of future incidents.
An organisation must ensure that it can identify, report, respond to, investigate and recover from security incidents.

GOV 6 includes the following requirements:

GOV 6.1 Establish an effective approach to managing security incidents

Ensure that your organisation has a robust and proactive approach to managing security incidents that the personnel understand and follow. Cyber incidents are only a matter of when, not if. A robust and effective approach will help ensure that the organisation is resilient and prepared.

  • Follow a structured approach for security incident management
  • Establish policies and procedures for managing security incidents
  • Prepare and test your incident response readiness

GOV 6.2 Ensure that security incidents are detected and raised

Ensure that your personnel understand their responsibilities, can detect that an incident has happened, and raises it to the appropriate team for assessment and investigation as quickly as possible.

  • Require personnel to raise security incidents and make it easy for them to do so
  • Establish mechanisms to quickly detect and respond to security incidents

GOV 6.3 Record and assess security incidents

Recording and tracking security incidents gives valuable insights into an organisation’s security environment and performance. For instance, repeated minor security incidents could be a symptom of poor personnel awareness and a need for more security awareness training.

  • Implement methods for recording and assessing the impact of security incidents

GOV 6.4 Report security incidents to relevant agencies

Ensure that your security incident team understand their responsibilities for reporting security incidents to other relevant agencies and build these into your security incident management processes.

  • Report certain security incidents to other agencies
  • Report security incidents involving holders of national security clearances
  • Report cyber security incidents to the National Cyber Security Centre
  • Report security incidents involving Cabinet material to the Cabinet Office
  • Report criminal incidents to law enforcement bodies
  • Include these details when you report major security incidents

GOV 6.5 Investigate, respond to, and manage security incidents

Security incidents can result in security investigations, disciplinary action, and/or criminal investigation. While investigations are underway, interim measures may be necessary to protect people, information, or assets at risk.

  • Investigate security incidents
  • Take interim measures while investigations are underway
  • When appropriate, involve others in security investigations

GOV 6.6 Learn from security incidents

Corrective action must be taken in response to relevant security incidents but also organisations should consider use of other monitoring and analysis practices to learn and reduce the likelihood of future incidents (such as root cause analysis, and post security incident reviews).

  • Monitor and measures incident management effectiveness
  • Conduct post-incident reviews when appropriate
  • Research incident management practice practices and security trends.

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 6 mandatory requirement.

Guidance and resources

GOV 7

Be able to respond to increased threat levels

Develop plans and be prepared to implement heightened security levels in emergencies or situations where there is an increased threat to your people, information, or assets.

Be prepared to increase heightened security levels in emergencies or situations of increasing security risks. Security alert levels communicate information about the security measures an organisation uses to reduce risks in emergency situations and other times of heightened risk. Alert levels also allow an organisation to scale its security measures, so they are appropriate to the type of incident and can change easily as risks increase or decrease.

GOV 7 includes the following requirements:

GOV 7.1 Identify sources of risk for heighted security alert levels

Organisations need to be ready to respond to emergency and increased security risk situations. Example events or threats include protests, demonstrations, bomb threats, threats of harm to a staff member, or other health and safety events such as fires, floods or natural disasters.  Use all types of risk information including site security plans, health and safety plans, risk assessments, risk management plans, business continuity plans, and security incident reviews. 

  • Use internal and external sources of information to inform response planning

GOV 7.2 Develop alert levels

Developing alert levels helps an organisation to apply security measures quickly before or during an event. A quick response can increase the ability to protect people, information, and assets. Refer to Security Governance Appendix C: Developing alert levels guidance for more information.

  • Establish alert levels that address all types of emergency and security alerts

GOV 7.3 Plan your response during heightened security alerts

Organisations need to identify the security measures it will use and develop response plans in line with the risks they are exposed to. Refer to example measures in the Operational security measures for alert levels [PDF, 44 KB] guidance.

  • Determine your security measures at different alert levels
  • Develop a plan for changing security alert levels

GOV 7.4 Monitor the risk environment and change alert levels when necessary

Organisations need to establish mechanisms to monitor the risk environment to ensure they can change alert levels and kick off response plans as quickly as possible during the event. 

  • Change alert levels when necessary
  • Debrief after changing alert levels

GOV 7.5 Review and update your processes

Organisations also need to practice their responses and learn from events to ensure that you identify gaps and improve your response performance.

  • Practice, review, and improve alert response processes.

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 7 mandatory requirement.

Guidance and resources

GOV 8

Assess your capability

Use an annual evidence-based assessment process to provide assurance that your organisation’s security capability is fit-for-purpose. Provide an assurance report to Government through the Protective Security Requirements team if requested.

Ongoing improvement in protective security requires a cycle of assessing and managing risks in an ever-changing environment. By using a self-assessment cycle, the organisation can:

  • identify needs for security measures
  • evaluate the effectiveness of existing protective security practices
  • prioritise and plan the focus areas and actions to take to improve protective security and effectively manage its security risks
  • report back to Government on current capability and improvement plans.

If your organisation is new to the PSR framework, your goals will be different to other organisations who have been on the protect security journey for a while. See Security Governance Appendix D: PSCMM improvement goals for organisations new to PSR for additional guidance.

GOV 8 has the following requirements:

GOV 8.1 Monitor and measure your protective security performance

GOV 8.2 Assess your protective security capability

GOV 8.3 Set your protective security goals for improvement

GOV 8.4 Provide assurance of your protective security capability and goals

GOV 8.5 Report on your protective security capability and improvement plans.

 

Refer to the PSR Policy Framework documents for details on the required and recommended measures to comply with the GOV 8 mandatory requirement.

Guidance and resources