This is a report of changes between nzism-data/NZISM-FullDoc-V.3.6-September-2022.xml and nzism-data/NZISM-ISM Document-V.-3.8-September-2024.xml.
| CID | Title | Classifications | Compliances | Text |
|---|---|---|---|---|
| 7524 | 11.1.15.C.01. | All Classifications | Must | Agencies wishing to permit the use of Bluetooth MUST develop a policy that details the circumstances under which Bluetooth usage is permitted, and situations where it is not to be used. |
| 7525 | 11.1.15.C.02. | All Classifications | Must | The policy position MUST include information about Bluetooth security controls that are to be used, and methods for verifying that the controls are in place and are effective. |
| 7526 | 11.1.16.C.01. | All Classifications | Must | Agencies MUST ensure that Bluetooth pairing is only established between authorised devices. (Unless a gateway is being used, paired devices are considered to operate at the same security classification level). |
| 7527 | 11.1.16.C.02. | All Classifications | Should | Agencies SHOULD ensure that Bluetooth discovery of devices is disabled unless a new pairing connection is being established. |
| 7528 | 11.1.16.C.03. | All Classifications | Should | Agencies SHOULD ensure that Bluetooth device pairing only occurs at a location where only authorised persons have access. |
| 7529 | 11.1.16.C.04. | All Classifications | Should | Agencies SHOULD ensure that Bluetooth pairings are removed when they are no longer required. |
| 7530 | 11.1.17.C.01. | All Classifications | Must | Agencies using Bluetooth MUST use the most secure configuration supported by the paired devices. |
| 7531 | 11.1.17.C.02. | All Classifications | Should | Agencies SHOULD identify the:
for devices used to form Bluetooth connections, and ensure they are used to inform risk decisions on the use of Bluetooth. |
| 7532 | 11.1.17.C.03. | All Classifications | Should | Agencies SHOULD ensure that new Bluetooth connections between devices are authenticated using explicit user actions, such as entry of a numeric code, confirmation of a matching PIN, or other affirming action, such as challenge-response process. |
| 7533 | 11.1.18.C.01. | Unclassified/In-Confidence | Should | Agencies using Bluetooth between devices to transfer UNCLASSIFIED or IN-CONFIDENCE information SHOULD ensure that connections meet NZISM standards for authentication and use Approved Cryptographic Algorithms for encryption and message integrity. |
| 7534 | 11.1.18.C.02. | Restricted/Sensitive | Must | Agencies using Bluetooth between devices to transfer RESTRICTED or SENSITIVE information MUST ensure that connections meet NZISM standards for authentication and use Approved Cryptographic Algorithms for encryption and message integrity. |
| 7535 | 11.1.18.C.03. | Restricted/Sensitive | Must | If Bluetooth specifications do not support these approved encryption methods, organisations MUST do a risk assessment and use the exception or waiver process to accept this risk. |
| 7519 | 15.2.36.C.03 | All Classifications | Must | Agencies MUST manage “received DMARC messages” in accordance with the agency’s published DMARC policy. |
| 7520 | 15.2.36.C.05 | All Classifications | Should | Agencies SHOULD produce failure reports and aggregate reports according to the agency’s DMARC policies. |
| 7521 | 15.2.48.C.01. | All Classifications | Should | Agencies SHOULD enable MTA-STS to prevent the unencrypted transfer of emails between complying servers. |
| 7522 | 15.2.48.C.02. | All Classifications | Must | Agencies MUST use TLS 1.2 or above when implementing MTA-STS. |
| 7523 | 15.2.48.C.03. | All Classifications | Should | Agencies SHOULD enable TLS reporting when implementing MTA-STS. |
| 7511 | 23.4.13.C.01. | All Classifications | Must | Agencies MUST have a defined exit strategy for each public cloud service they consume, including a process by which their data can be retrieved and erased from the cloud service as part of contract termination. |
| 7512 | 23.4.13.C.02. | All Classifications | Must | Agencies MUST ensure all data they need to retain is retrieved from the cloud service provider prior to decommissioning. |
| 7513 | 23.4.13.C.03. | All Classifications | Must | Agencies MUST have assurance that no agency-owned data is retained on the cloud service being decommissioned. |
| CID | Title | Classifications | Compliances | Text |
|---|---|---|---|---|
| 2557 | 11.2.5.C.01. | Confidential, Secret, Top Secret | Must | Agencies intending to use fax machines or MFDs to send classified information MUST comply with additional requirements. Contact the GCSB for further details. |
| CID | Title | Classifications | Compliances | Text |
|---|---|---|---|---|
| 177 | 1.2.15.C.01. | All Classifications | Must | Agencies undertaking system design activities for in-house or out-sourced projects MUST use the latest version of thise manualNZISM for information security requirements. |
| 178 | 1.2.15.C.02. | All Classifications | Must | When GCSB makes a determination that newly introduced standard, policy or guideline within this manuale NZISM, or any additional information security policy, is of particular importance, agencies MUST comply with any new specified requirements and implementation timeframes. |
| 199 | 2.1.49.C.01. | All Classifications | Must | Security personnel MUSHOULDT familiarise themselves with the information security roles and services provided by New Zealand Government organisations. |
| 7211 | 2.4.13.C.06. | All Classifications | Should | Agencies SHOULD consider the following factors when prioritising the quantum vulnerable systems:Is the system a high value asset based on agency requirements?Does the system protect sensitive information (e.g., key stores, passwords, root keys, signing keys, personally identifiable information, and classified information)?Do other systems (internal or external to the agency) depend on the cryptographic protections in place on the quantum vulnerable system?How long does the data need to be protected? |
| 781 | 5.2.3.C.02. | All Classifications | Should | The Information Security Policy (SecPol) SHOULD include topics such as: accreditation processes; accreditation processes;personnel responsibilities;configuration control; access control; access control;networking and connections with other systems; physical security and media control; physical security and media control;emergency procedures and information security incident management;vulnerability disclosure; change management; and change management; andinformation security awareness and training. |
| 1048 | 6.1.9.C.01. | All Classifications | Should | Agencies SHOULD review the components detailed in the table below. Agencies SHOULD also ensure that any adjustments and changes as a result of any vulnerability analysis are consistent with the vulnerability disclosure policy.ComponentReviewInformation security documentationThe SecPol, Systems Architecture, SRMPs, SSPs, SitePlan, SOPs, the VDP, the IRP, and any third party assurance reports.DispensationsPrior to the identified expiry date.Operating environmentWhen an identified threat emerges or changes, an agency gains or loses a function or the operation of functions are moved to a new physical environment.ProceduresAfter an information security incident or test exercise. System security System securityItems that could affect the security of the system on a regular basis.ThreatsChanges in threat environment and risk profile.NZISMChanges to baseline or other controls, any new controls and guidance. |
| 1153 | 7.1.7.C.01. | Top Secret, Confidential, Secret | Must | Agencies MUST develop, implement and maintain tools and procedures covering the detection of potential information security incidents, incorporating:user awareness and training;counter-measures against malicious code, known attack methods and types; intrusion detection strategies; intrusion detection strategies;data egress monitoring & control; access control anomalies; audit analysis; access control anomalies;audit analysis;system integrity checking; andvulnerability assessments. |
| 1154 | 7.1.7.C.02. | All Classifications | Should | Agencies SHOULD develop, implement and maintain tools and procedures covering the detection of potential information security incidents, incorporating:user awareness and training;counter-measures against malicious code, known attack methods and types; intrusion detection strategies; intrusion detection strategies;data egress monitoring & control; access control anomalies; audit analysis; access control anomalies;audit analysis;system integrity checking; andvulnerability assessments. |
| 1285 | 7.3.8.C.03. | All Classifications | Should | When a data spill involving classified information or contaminatingon of classified systems occurs and systems cannot be segregated, or isolated agencies SHOULD immediately contact theNCSCfor further advice. |
| 1403 | 8.4.10.C.01. | All Classifications | Must | Agencies MUST ensure that when secure areas are non-operational or when work areas are unoccupied IT equipment with media is secured in accordance with the minimum physical security requirements for storing classified information as specified in the PSR Management protocol for physical security –Physical Security of youfor ICT assets and facilities, with supporting document –Storage requirements for electronic information in ICT facilities. |
| 1458 | 9.1.6.C.02. | All Classifications | Should | Agencies SHOULD ensure that information security awareness and training includes information on:the purpose of the training or awareness program;any legislative or regulatory mandates and requirements;any national or agency policy mandates and requirements; agency security appointments and contacts; agency security appointments and contacts;the legitimate use of system accounts, software and classified information;the security of accounts, including shared passwords;authorisation requirements for applications, databases and data;the security risks associated with non-agency systems, particularly the Internet; reporting any suspected compromises or anomalies; reporting any suspected compromises or anomalies;reporting requirements for information security incidents, suspected compromises or anomalies;classifying, marking, controlling, storing and sanitising media;protecting workstations from unauthorised access;informing the support section when access to a system is no longer needed;observing rules and regulations governing the secure operation and authorised use of systems; andsupporting documentation such as SOPs and user guides. |
| 1487 | 9.2.12.C.01. | All Classifications | Should | Agencies SHOULD:maintain a secure record of: all authorised system users; their user identification; all authorised system users;their user identification;why access is required;role and privilege level,who provided the authorisation to access the system; when the authorisation was granted; and when the authorisation was granted; andkeep a copy of the acknowledgement signed by the individual granted a clearance; andmaintain the record, for the life of the system or information to which access is granted, or the length of employment, whichever is the longer. |
| 1491 | 9.2.13.C.02. | All Classifications | Must | All system users MUST:hold a security clearance at least or other authorisation appropriate for the system classification; orhave been granted access in accordance with the requal to the system classification; or have been granted access in accordance with the requirements in the irements in thePSRfor emergency access. |
| 1505 | 9.2.17.C.02. | All Classifications | Must | Agencies granting limited limitedhigher access to information or systems MUST ensure that:the requirement to grant limited higher access is temporary in nature and is an exception rather than the norm;an ITSM has recommended the limited higher access;a cessation date for limited higher access has been set;the access period does not exceed two months;the limited higher access is granted on an occasional NOT non-ongoing basis;the system user is not granted privileged access to the system;the system user’s access is formally documented; andthe system user’s access is approved by the CISO. |
| 1508 | 9.2.18.C.01. | All Classifications | Must | Agencies granting limited limitedhigher access to a system MUST ensure that:the approval for access is formally acknowledged and recorded; and eithereffective controls are in place to restrict access only onlyto classified information that is necessary to undertake the system user’s duties; orthe system user is continually supervised by another system user who has the appropriate security clearances to access the system. |
| 2230 | 10.1.45.C.01. | All Classifications | Must | Agencies MUST comply with the cable and conduit colours specified in the following table. Classification ClassificationCable colourCompartmented Information (SCI)Orange/Yellow/Teal or other colourTOP SECRET Red SECRET RedSECRETBlueCONFIDENTIALGreenRESTRICTED and all lower classificationsBlack |
| 2241 | 10.1.47.C.02. | All Classifications | Must Not | Agencies MUST NOT deviate from the approved fibre cable combinations for shared conduits and reticulation systems as indicated below.GroupApproved combination1UNCLASSIFIEDRESTRICTED2CONFIDENTIAL SECRET SECRET3TOP SECRETOther Special Networks |
| 2387 | 10.5.4.C.01. | All Classifications | Must | Agencies MUST comply with the conduit label colours specified in the following table. Classification ClassificationCable colourCompartmented Information (SCI)Orange/Yellow/Teal or other colourTOP SECRET Red SECRET RedSECRETBlueCONFIDENTIALGreenRESTRICTED and all lower classificationsBlack |
| 2492 | 11.1.19.C.01. | Confidential, Top Secret, Secret | Must | Agencies MUST complete a technical evaluation of the secure area, consult the relevant technical authority and seek approval from the Accreditation Authority before permitting the use of Bluetooth keyboards or other Bluetooth devices are permittedevices. |
| 2494 | 11.1.19.C.02. | Confidential, Top Secret, Secret | Must Not | Agencies using Bluetooth keyboards or other Bluetooth devices MUST NOT allow:line of sight and reflected communications travelling into an unsecure area; .multiple kBlueybtoards or other devices at different classifications in the same area; other Bluetooth or infrared devices to be brought into range of the keyboard or its receiving device/port; and Bluetooth keyboards or other devices to be operated in areas with unprotected (non-shielded/curtained) windows. |
| 2495 | 11.1.19.C.03. | Top Secret, Confidential, Secret | Must Not | Agencies MUST NOT useallow Bluetooth devices intor wisecureless keyboardeas unless wiauthorin a RF screened buily the Accreditationg Authority. |
| 2483 | 11.2.14.C.01. | Top Secret, Secret, Confidential | Must Not | Wireless RF or IR pointing devices MUST NOT be used in secure areas unless usapproved wby the Accredithation Authority and appropriate RF screened building or IRF mitigations are implemented. |
| 2489 | 11.2.15.C.03. | All Classifications | Should | Agencies using IR devinfrarced keyboards SHOULD ensure that infrathe IR red ceiver/port is are positioned to prevent line of sight and freflected communications travhelling into an unsecure area boundary. |
| 2767 | 11.5.16.C.03. | All Classifications | Must | Where the use of personal wearable devices is permitted on medical grounds and used within a corporate or agency environment, agencies MUST ensure any relevant legislation and regulation pertaining to the protection of Personally Identifiable Information (PII)personal information is followed. |
| 2999 | 11.6.67.C.02. | All Classifications | Should | Agencies SHOULD follow the guidance for passwords management in the NZISM (Chapter 16 – Access Ccontrol and passwords). |
| 3006 | 11.6.69.C.01. | All Classifications | Must | Agencies MUST develop and implement incident identification and management processes in accordance with this manual (SeeChapter 5 – Information Security Documentation,Chapter 6 – Information Security Monitoring,Chapter 7 – Information Security Incidents,Chapter 9 – Personnel Security and andChapter 16 – Access Control and passwords). |
| 3010 | 11.6.70.C.01. | All Classifications | Should | Agencies SHOULD consider secure disposal procedures and incorporate these into the RFID Usage Policy. Refer also toChapter 13 – DMedia and IT equipment management, decommissioning and Ddisposal. |
| 3180 | 11.7.34.C.01. | All Classifications | Must | Agencies MUST develop and implement incident identification and management processes in accordance with this manual (SeeChapter 5 – Information Security Documentation,Chapter 6 – Information Security Monitoring,Chapter 7 – Information Security Incidents,Chapter 9 – Personnel Security and andChapter 16 – Access Controlcontrol and passwords). |
| 3189 | 11.7.35.C.01. | All Classifications | Should | Agencies SHOULD consider secure disposal procedures and incorporate these into the Access Card Usage Policy. Refer also toMedia Chand IT equipment managerment, 13 – Ddecommissioning and Ddisposal. |
| 2537 | 11.8.3.C.01. | All Classifications | Must | Agencies MUST develop a policy governing the use of fax machines, MFDs, and network printers. and fax machines, |
| 2543 | 11.8.4.C.01. | Top Secret, Secret, Confidential | Must | Agencies sending classified fax messages MUST ensure that the fax message is encrypted to an appropriate level when communicated over unsecured telecommunications infrastructure or the public switched telephone network. |
| 2545 | 11.8.4.C.02. | Top Secret, Confidential, Secret | Must | Agencies MUST have separate MFDs or fax machines or MFDs for sending classified fax messages and messages classified RESTRICTED and below. |
| 2578 | 11.8.8.C.01. | All Classifications | Must Not | Agencies MUST NOT permit MFDs connected to computer networks to be used to scan or copy classified documents above the classification of the connected network. |
| 2581 | 11.8.9.C.01. | All Classifications | Should | Agencies SHOULD ensure that MFDs and fax machines and MFDs are located in an areas where their use can be observed. |
| 2590 | 11.8.10.C.02 | Secret, Top Secret, Confidential | Must | Any storage devices, drums or cartridges with memory chips removed during maintenance or servicing MUST be disposed of following the processes prescribed inChapter 13 - Media and IT equipment Management, Decommissioning and Disposal. |
| 2591 | 11.8.10.C.03 | Confidential, Secret, Top Secret | Must | Toner cartridges MUST have the memory chip removed before the cartridge is recycled or otherwise disposed of. The memory chip MUST be disposed of following the processes prescribed inChapter 13 - Media and IT equipment Management, Decommissioning and Disposal. |
| 2593 | 11.8.10.C.05 | All Classifications | Should | Any storage devices, drums or cartridges with memory chips removed during maintenance or servicing SHOULD be disposed of following the processes prescribed inChapter 13 - Media and IT equipment Management, Decommissioning and Disposal. |
| 2604 | 11.8.12.C.01 | Top Secret, Confidential, Secret | Must | Any storage devices, drums, cartridge memory chips or other components that may contain data or copies of documents MUST be disposed of following the processes prescribed inChapter 13 - Media and IT equipment Management, Decommissioning and Disposal. |
| 2606 | 11.8.12.C.02 | All Classifications | Should | Any storage devices, drums, cartridge memory chips or other components that may contain data or copies of documents SHOULD be disposed of following the processes prescribed inChapter 13 - Media and IT equipment Management, Decommissioning and Disposal. |
| 3306 | 12.1.32.C.03. | All Classifications | Must | Agencies selecting high assurance products and HGACE MUST contact the GCSB and comply with any product specific requirements, before any purchase is made. |
| 3318 | 12.1.34.C.01. | All Classifications | Must | Agencies procuring high assurance products and HGACE MUST contact the GCSB and comply with any product specific delivery procedures. |
| 3387 | 12.2.5.C.01. | All Classifications | Must | Agencies MUST ensure that high assurance products and HGACE are installed, configured, operated and administered in accordance with all product specific policy. |
| 3404 | 12.2.6.C.02. | All Classifications | Must Not | High assurance products and HGACE MUST NOT be used in unevaluated configurations. |
| 3427 | 12.3.5.C.01. | Confidential, Top Secret, Secret | Must | Agencies MUST clearly label all IT equipment capable of storing or processing classified information, with the exception of HGACE, with the appropriate protective marking. |
| 3434 | 12.3.7.C.01. | All Classifications | Should | Agencies SHOULD seek GCSB authorisation before applying labels to external surfaces of HGACE. |
| 3450 | 12.4.4.C.03. | All Classifications | Must Not | Agencies MUST NOT patch high assurance products or HGACE without the patch being approved by the GCSB. |
| 3481 | 12.5.3.C.01. | All Classifications | Must | Agencies MUST seek GCSB approval before undertaking any repairs to high assurance products or HGACE. |
| 3549 | 12.6.5.C.03. | All Classifications | Must | Agencies MUST contact the GCSB and comply with any requirements for the disposal of HGACE. |
| 3832 | 13.1.10.C.01. | All Classifications | Should | Agencies SHOULD undertake a risk assessment with consideration given to proportionality in respect of:scale and impact of the processes; data; data;users;licences;usage agreements; andservice to be migrated or decommissioned. |
| 4176 | 13.4.10.C.01. | All Classifications | Must | Agencies MUST destroy the following media types prior to prior todisposal, as they cannot be effectively sanitised: microfiche; microfilm; optical discs; microfiche;microfilm;optical discs;printer ribbons and the impact surface facing the platen;programmable read-only memory (PROM, EPROM, EEPROM);flash memory and solid state or hybrid data storage devices;read-only memory; andfaulty magnetic media that cannot be successfully sanitised. |
| 4184 | 13.4.12.C.01. | All Classifications | Must | Following sanitisation, volatile media MUST be treated as indicated in the table below.Pre-sanitisation classification / EndorsementPost-sanitisation classification / EndorsementNew Zealand Eyes Only (NZEO) EndorsementNZEOTOP SECRETTOP SECRET SECRET SECRET SECRETSECRETCONFIDENTIALUNCLASSIFIEDRESTRICTED and all lower classificationsUNCLASSIFIED |
| 4200 | 13.4.14.C.01. | All Classifications | Must | Following sanitisation, non-volatile magnetic media MUST be treated as indicated in the table below.Pre-sanitisation classificationPost-sanitisation classificationNew Zealand Eyes Only (NZEO) EndorsementNZEO TOP SECRET TOP SECRET SECRET SECRET TOP SECRETTOP SECRETSECRETSECRETCONFIDENTIALUNCLASSIFIED RESTRICTED RESTRICTEDUNCLASSIFIED |
| 4212 | 13.4.17.C.01. | All Classifications | Must | Following sanitisation, non-volatile EPROM and EEPROM media MUST be treated as indicated in the table below.Pre-sanitisation classificationPost-sanitisation classificationNew Zealand Eyes Only (NZEO) EndorsementNZEO TOP SECRET TOP SECRET SECRET SECRET TOP SECRETTOP SECRETSECRETSECRETCONFIDENTIALUNCLASSIFIED RESTRICTED RESTRICTEDUNCLASSIFIED |
| 4218 | 13.4.19.C.01. | All Classifications | Must | Following sanitisation, non-volatile flash memory media MUST be treated as indicated in the table below.Pre-sanitisation classificationPost-sanitisation classificationNew Zealand Eyes Only (NZEO) EndorsementNZEO TOP SECRET TOP SECRET SECRET SECRET TOP SECRETTOP SECRETSECRETSECRETCONFIDENTIALCONFIDENTIAL RESTRICTED RESTRICTEDUNCLASSIFIED |
| 4276 | 13.5.23.C.01. | All Classifications | Must | To destroy media and IT Equipment agencies MUST use at least one of the methods shown in the following table.ItemDestruction methodsFurnace/ IncineratorHammer millDisintegratorGrinder/ SanderCuttingDegausserMagnetic floppy disks Yes Yes Yes No Yes Yes YesYesYesNoYesYesMagnetic hard disks Yes Yes Yes Yes No Yes YesYesYesYesNoYesMagnetic tapes Yes Yes Yes No Yes Yes YesYesYesNoYesYesOptical disks Yes Yes Yes Yes Yes No YesYesYesYesYesNoElectrostatic memory devices Yes Yes Yes Yes No No YesYesYesYesNoNoSemi-conductor memory Yes Yes Yes No No No YesYesYesNoNoNoOther Circuit Boards Yes Yes Yes No No NoYesYesYesNoNoNo |
| 4343 | 13.5.25.C.01. | All Classifications | Must | Agencies MUST, at minimum, store and handle the resulting waste for all methods, in accordance with the classification given in the table below.Initial media or IT Equipment classificationScreen aperture size particles can pass throughLess than or equal to3mm Treat as Treat asLess than or equal to6mm Treat as Treat asTOP SECRETUNCLASSIFIED RESTRICTED SECRET RESTRICTEDSECRETUNCLASSIFIED RESTRICTED RESTRICTEDCONFIDENTIALUNCLASSIFIED RESTRICTED RESTRICTED RESTRICTEDRESTRICTEDUNCLASSIFIEDUNCLASSIFIEDParticle size: measured in any direction, should not exceed stated measurement. |
| 1593 | 14.3.6.C.02. | All Classifications | Should | An agency’s Web proxy SHOULD authenticate system users and provide logging that includes at least the following details about websites accessed:address (uniform resource locator);time/date; system user; system user;internal IP address; andexternal IP address. |
| 6019 | 15.2.36.C.01. | All Classifications | Must | Before implementing DMARC agencies MUSHOULDT:Create a DMARC policy;List all domains, in particular those used for the sending and/or receiving of email;Review the configuration of SPF and DKIM for all active domains and all published domains; andEstablish one or more monitored inboxes to receive DMARC reports. |
| 6020 | 15.2.36.C.02 | All Classifications | Must | Agencies MUSHOULDT enable DMARC with a policy of p=reject for all email originating from or received by their domain(s), including: sending domain o.See 15.2.16for a recommended approach wners SHOULD puhere a domain is used for sending and/or receiving email and disruption would cause a blish a DMARC record with a related DNS entry advising mail receivers of the characteristics of messages purporting to originate from the sender’s domain; received DMARC messages SHOULD be managed in accordance with the agency’s published DMARC policy; and agencies SHOULD produce failure reports and aggregate reports according to the agency’s DMARC policies.usiness impact. |
| 6021 | 15.2.36.C.04 | All Classifications | Must | Agencies MUSHOULDT review DMARC reports on a regular basis and address any identified anomalies or security issues. |
| 1745 | 15.2.37.C.01. | All Classifications | Should | Agencies SHOULD configure the following gateway filters:inbound and outbound email, including any attachments, that contain:malicious code;content in conflict with the agency’s email policy;content that cannot be identified;deny listed or unauthorised filetypes; andencrypted content, when that content cannot be inspected for malicious code or authenticated as originating from a trusted source; emails addressed to internalemails addressed to internal-use only email aliases with source addresses located from outside the domain; andall emails arriving via an external connection where the source address uses an internal agency domain name. |
| 1768 | 15.2.42.C.01 | All Classifications | Should | Agencies SHOULD onlysend notification of undeliverable, bounced, or blocked emails to senders that can be verified via SPF or other trusted means. |
| 1774 | 15.2.44.C.01 | All Classifications | Must | Agencies MUSHOULDT disable open email relaying so that email servers will only relay messages destined for the agency’s domain(s) and those originating from authorised systems or users within that domain. |
| 1793 | 15.2.49.C.02. | All Classifications | Must | Agencies MUSHOULDT:use a hard fail SPF record when specifying email servers; anduse SPF or Sender ID to verify the authenticity of incoming emails. |
| 1794 | 15.2.49.C.03 | All Classifications | Should | Agencies SHOULD refer to the SPF recommendations in IETF’s RFC 447208. |
| 1798 | 15.2.50.C.01 | All Classifications | Must | Agencies MUSHOULDT enable DKIM signing on all email originating from their domain. |
| 1797 | 15.2.50.C.02 | All Classifications | Must | Agencies MUSHOULDT use DKIM in conjunction with SPF. |
| 1827 | 16.1.31.C.01. | All Classifications | Must | Agencies MUST:develop, implement and maintain a set of policies and procedures covering all system users’: identification; authentication; authorisation; identification;authentication;authorisation;privileged access identification and management; andmake their system users aware of the agency’s policies and procedures. |
| 1901 | 16.1.48.C.03. | All Classifications | Should | Agency logon banners SHOULD cover issues such as:the system’s classification; access only being permitted to authorised system users; access only being permitted to authorised system users;the system user’s agreement to abide by relevant security policies;the system user’s awareness of the possibility that system usage is being monitored; the definition of acceptable use for the system; and the definition of acceptable use for the system; andlegal ramifications of violating the relevant policies. |
| 2001 | 16.6.7.C.01. | All Classifications | Should | A system management log SHOULD record the following minimum information:all system start-up and shutdown;service, application, component or system failures; maintenance activities; maintenance activities;backup and archival activities; system recovery activities; and system recovery activities; andspecial or out of hours activities. |
| 2009 | 16.6.9.C.01. | Top Secret, Secret, Confidential | Must | Agencies MUST log, at minimum, the following events for all software components: logons; failed logon attempts; logoffs; date and time; logons;failed logon attempts;logoffs;date and time;all privileged operations;failed attempts to elevate privileges;security related system alerts and failures;system user and group additions, deletions and modification to permissions; andunauthorised or failed access attempts to systems and files identified as critical to the agency. |
| 2013 | 16.6.10.C.02. | All Classifications | Should | Agencies SHOULD log, at minimum, the following events for all software components: user login; user login;all privileged operations;failed attempts to elevate privileges; security related system alerts and failures; security related system alerts and failures;system user and group additions, deletions and modification to permissions; andunauthorised or failed access attempts to systems and files identified as critical to the agency. |
| 2017 | 16.6.11.C.01. | All Classifications | Must | For each event identified as needing to be logged, agencies MUST ensure that the log facility records at least the following details, where applicable:date and time of the event;relevant system user(s) or processes; event description; success or failure of the event; event description;success or failure of the event;event source (e.g. application name); andIT equipment location/identification. |
| 2034 | 16.6.14.C.01. | All Classifications | Must | Agencies MUST develop and document event log audit requirements covering:the scope of audits; the audit schedule; the audit schedule;action to be taken when violations are detected;reporting requirements; androles and specific responsibilities. |
| 6561 | 17.2.27.C.02. | All Classifications | Should | Memorised secrets such as passwords SHOULD be salted and hashed using a suitable one-way key derivation function. See17.2.214. |
| 2726 | 17.5.8.C.02. | All Classifications | Should | Agencies that use logins without a password for automated purposes SHOULD disable:access from IP addresses that do not need access; port forwarding; agent credential forwarding; port forwarding;agent credential forwarding;X11 display remoting; andconsole access. |
| 3016 | 17.9.30.C.01. | All Classifications | Should | Agencies MSHOUST developLD a KMP whssenss the risks associated around key ownership, possession, avnd control against their own securimplty and business requiremented a cryptographic system using HGCP. |
| 3021 | 17.9.31.C.01. | All Classifications | Should | The table below describes the minimum contents which SHOULD be documented in the KMP.TopicContentObjectivesObjectives of the cryptographic system and KMP, including organisational aims.Refer to relevant NZCSIs.System descriptionThe environment.Maximum classification of information protected.Topology diagram(s) and description of the cryptographic system topology including data flows.The use of keys.Key algorithm.Key length.Key lifetime.Roles and administrative responsibilitiesDiagram(s) and description of the cryptographic system topology including data flows. The use of keys. Key algorithm. Key length. Key lifetime. Roles and administratiocuments roles and responsibilities, including, if releve responsibilities Documents roles and responsibilitiesant, including the: the COMSEC custodian, cryptographic systems administrator, record keeper, cloud service provider, and auditor.AccountingHow accounting will be undertaken for the cryptographic system.What records will be maintained.How records will be audited.Custodian; lassificationCryptographic systems administrator; lassification of the cryptographic system hardware.Classification of cryptographic system software.Classification of the cryptographic system documentation.Information security incidentsA description of the conditions under which compromise of key material should be declared.Recordferences to procedures to be followed when reporting and dealing with information security incidents.Key managementWho generates keeper; and ys.How keys are delivered.How keys are received.Key distribution, including local, remote and central.How keys are installed.How keys are transferred.How keys are stored.How keys are recovered.How keys are revoked.How keys are destroyed.Each time key information or material is accessed, details are captured in logs.Auditor. Accounting How accounting will be undertapproved access lists to cryptographic ken for the cryptographic system. What records will be maintained. How records will be audited. Classification Classification of the cryptographic system hardware. Classification of cryptographic system software. Classification of the cryptographic system documentation. Information security incidents A description of the conditions under which compromise of key material should be declared. ys.MaintenanceMaintaining the cryptographic system software and hardware.Destroying equipment and media.References to procedures to be followed when reporting and dealing with information security incidents. Key management Who generates keys. How keys are delivered. How keys are received. Key distribution, including local, remote and central. How keys are installed. How keys are transferred. How keys are stored. How keys are recovered. How keys are revoked. How keys are destroyed. Maintenance Maintaining the cryptographic system software and hardware. Destroying equipment and media. Vendor documentation.References Vendor documentation. Related policies.lated policies. |
| 3033 | 17.9.34.C.01. | All Classifications | Must | Agencies MUST hold and maintain an access register that records cryptographic system information such as:details of personnel with system administrator access; details of those whose system administrator access was withdrawn; details of system documents; details of those whose system administrator access was withdrawn;details of system documents;accounting activities; andaudit activities. |
| 4051 | 18.6.8.C.01. | All Classifications | Must | Agencies accessing a classified system and a less classified system via a peripheral switch MUST use an evaluated product with a level of assurance as indicated in the table below.High SystemLow system / Alternate Trust DomainRequired Level of Assurance RESTRICTED RESTRICTEDUNCLASSIFIEDEAL2 or PPCONFIDENTIALUNCLASSIFIED high assurance RESTRICTED high assurance high assuranceRESTRICTEDhigh assuranceCONFIDENTIAL high assurance SECRET high assuranceSECRETUNCLASSIFIED high assurance RESTRICTED high assurance high assuranceRESTRICTEDhigh assuranceCONFIDENTIAL high assurance SECRET high assurance high assuranceSECREThigh assuranceTOPSECRETUNCLASSIFIEDhigh assuranceRESTRICTEDhigh assuranceCONFIDENTIALhigh assuranceSECREThigh assuranceTOP SECRET UNCLASSIFIED high assurance RESTRICTED high assurance CONFIDENTIAL high assurance SECRET high assurance TOP SECRET high assurancehigh assurance |
| 4066 | 18.6.10.C.01. | All Classifications | Must | Cross-connection of security domains and Trust Zones MUST be enabled through an approved KVM, Gateway or Cross-Domain solution only.High systemLow system/ Alternate Trust DomainLevel of assurance RESTRICTED RESTRICTED& all lower classificationsUNCLASSIFIEDEAL2 or PPCONFIDENTIALUNCLASSIFIED high assurance RESTRICTED high assurance high assuranceRESTRICTEDhigh assuranceCONFIDENTIAL high assurance SECRET high assuranceSECRETUNCLASSIFIED high assurance RESTRICTED high assurance high assuranceRESTRICTEDhigh assuranceCONFIDENTIAL high assurance SECRET high assurance high assuranceSECREThigh assuranceTOP SECRETUNCLASSIFIED high assurance RESTRICTED high assurance high assuranceRESTRICTEDhigh assuranceCONFIDENTIAL high assurance SECRET high assurance high assuranceSECREThigh assuranceTOP SECRET high assurancehigh assurance |
| 3975 | 19.3.8.C.03. | All Classifications | Must | Agencies MUST use devices as shown in the following table for their gateway when connecting two networks of different classifications or two networks of the same classification but of different security domains.Your networkTheir networkYou requireThey requireRESTRICTED and belowUNCLASSIFIEDEAL4 firewallN/A RESTRICTED EAL2 or PP firewall EAL2 or PP firewall RESTRICTEDEAL2 or PP firewallEAL2 or PP firewallCONFIDENTIAL EAL2 or PP firewall EAL2 or PP firewallEAL4 firewall SECRET EAL2 or PP firewall SECRETEAL2 or PP firewallEAL4 firewallTOP SECRET EAL2 or PP firewall EAL2 or PP firewallConsultation with GCSBCONFIDENTIALUNCLASSIFIEDConsultation with GCSBN/A RESTRICTED RESTRICTEDEAL4 firewall EAL2 or PP firewall EAL2 or PP firewallCONFIDENTIAL EAL2 or PP firewall EAL2 or PP firewall SECRET EAL2 or PP firewall EAL2 or PP firewallEAL2 or PP firewallSECRETEAL2 or PP firewallEAL4 firewallTOP SECRET EAL2 or PP firewall EAL2 or PP firewallConsultation with GCSB SECRET SECRETUNCLASSIFIEDConsultation with GCSBN/A RESTRICTED RESTRICTEDEAL4 firewall EAL2 or PP firewall EAL2 or PP firewallCONFIDENTIALEAL4 firewall EAL2 or PP firewall SECRET EAL2 or PP firewall EAL2 or PP firewall EAL2 or PP firewallSECRETEAL2 or PP firewallEAL2 or PP firewallTOP SECRET EAL2 or PP firewall EAL2 or PP firewallEAL4 firewallTOP SECRETUNCLASSIFIEDConsultation with GCSBN/A RESTRICTED RESTRICTEDConsultation with GCSB EAL2 or PP firewall EAL2 or PP firewallCONFIDENTIALConsultation with GCSB EAL2 or PP firewall SECRET EAL2 or PP firewallSECRETEAL4 firewall EAL2 or PP firewall EAL2 or PP firewallTOP SECRETEAL4 firewallEAL4 firewall |
| 4015 | 19.4.4.C.01. | All Classifications | Must | Agencies MUST use devices as shown in the following table for controlling the data flow of one-way gateways between networks of different classifications.High networkLow networkYou require RESTRICTED RESTRICTEDUNCLASSIFIEDEAL2 or PP diode RESTRICTED RESTRICTEDEAL2 or PP diodeCONFIDENTIALUNCLASSIFIED high assurance diode RESTRICTED high assurance diode high assurance diodeRESTRICTEDhigh assurance diodeCONFIDENTIAL high assurance diode SECRET high assurance diodeSECRETUNCLASSIFIED high assurance diode RESTRICTED high assurance diode high assurance diodeRESTRICTEDhigh assurance diodeCONFIDENTIAL high assurance diode SECRET high assurance diode high assurance diodeSECREThigh assurance diodeTOP SECRETUNCLASSIFIED high assurance diode RESTRICTED high assurance diode high assurance diodeRESTRICTEDhigh assurance diodeCONFIDENTIAL high assurance diode SECRET high assurance diode high assurance diodeSECREThigh assurance diodeTOP SECRET high assurance diodehigh assurance diode |
| 4710 | 19.5.24.C.07. | All Classifications | Must | Agencies procuring or using VoIP or UC services to be used by multiple agencies MUST ensure all interested parties formally agree to the risks, controls and any residual risks of such VoIP and UC services. The lead agency normally has this responsibility (seeChapter 2 - Information Security services within Government and andChapter 4 - System Certification and Accreditation). |
| 4749 | 19.5.28.C.02. | All Classifications | Must | Agencies MUST develop and implement incident identification and management processes in accordance with this manual (SeeChapter 6 – Information Security Monitoring,Chapter 7 – Information Security Incidents,Chapter 9 – Personnel Security and andChapter 16 – Access Controlcontrol and passwords). |
| 4239 | 20.1.11.C.01. | Confidential, Secret, Top Secret | Must | When agencies export formatted textual data with no free text fields and all fields have a predefined set of permitted formats and data values, agencies MUST implement the following controls:protective marking checks;data validation and format checks;size limits;keyword checks;identify unexpected attachments or embedded objects; log each event; and log each event; andmonitoring to detect overuse/unusual usage patterns. |
| 4825 | 22.1.22.C.06. | All Classifications | Should Not | Agencies SHOULD NOT use cloud services hosted offshoreunless:privacy, information sensitivity and information value has been fully assessed by the agency;a comprehensive risk assessment is undertaken by the agency;controls to manage identified risks have been specified by the agency; andthe cloud service provider is able to provide adequate assurance that these controls have been properly implemented before beforethe agency uses the cloud service. |
| 4843 | 22.1.25.C.02. | All Classifications | Must | Agencies MUST develop and implement incident identification and management processes in accordance with this manual (SeeChapter 6 – Information Security Monitoring,Chapter 7 – Information Security Incidents,Chapter 9 – Personnel Security and andChapter 16 – Access Control). |
| 7353 | 23.1.55.C.01. | All Classifications | Must | Agencies MUST clearly identify and understand their cloud service provider’s security responsibilities for each service consumed, and the aspects of security that the agency is responsible for, prior priorto implementation or adoption of the service. |
| 7397 | 23.2.18.C.01. | All Classifications | Should | Agencies SHOULD obtain regular assurance checks on cloud service providers, ensuring that they harve been undertaken by a suitably qualified assessor. |