Agencies SHOULD consider placement of tags and location of readers to avoid unnecessary electromagnetic radiation.
11.7.32.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3166]
Agencies SHOULD consider and select other physical controls in accordance with thePSR.
11.7.33. Card Data Protection
11.7.33.R.01. Rationale
Cards are invariably retained by the card holder and subject to loss, theft or being misplaced. Cards are also not always within the control of the
card holder outside of normal office hours. Measures to protect cards in these situations are fundamental to the maintenance of the integrity
and security of the access control system.
11.7.33.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:3171]
Agencies MUST follow the requirements of the NZISM in the selection and implementation of cryptographic protocols and algorithms, and in key
management, detailed in Chapter 17 - Cryptography.
11.7.33.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3173]
Agencies SHOULD encrypt data before it is written to cards.
11.7.33.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3175]
Agencies SHOULD consider the use of cards systems incorporating Secure Access Modules (SAMs).
11.7.34. Incident Management
11.7.34.R.01. Rationale
Incident management and audit procedures, logging and time stamps help detect and manage security breaches. These are important tools in
protecting systems and managing security breaches.
11.7.34.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:3180]
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 Chapter 16 – Access Control).
11.7.35. Disposal
11.7.35.R.01. Rationale
Card disposal and recycling procedures that permanently disable or destroy sensitive data reduces the possibility that they could be used later
for tracking or targeting, and prevents access to sensitive data stored on cards. In addition the continued operating presence of a card after it
has performed its intended function can pose an unauthorised access, business intelligence or privacy risk, including tracking and targeting of
personnel or access to sensitive data on the access card.
11.7.35.R.02. Rationale
Disposal may be undertaken by electronically by using a card’s wipe feature or using a strong electromagnetic field to permanently deactivate
a tag’s circuitry. Alternatively physical destruction can be achieved by tearing or shredding. Where a tag supports an electronic deactivation
mechanism, tags should be electronically deactivated before physical destruction.
11.7.35.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3189]
Agencies SHOULD consider secure disposal procedures and incorporate these into the Access Card Usage Policy. Refer also toChapter 13 –
Decommissioning and Disposal.
12. Product Security
12.1. Product Selection and Acquisition
Objective
12.1.1. Products providing security functions for the protection of classified information are formally evaluated in order to provide a degree of assurance over
the integrity and performance of the product.
Context
Scope
12.1.2. This section covers information on the selection and acquisition of any product that provide security functionality for the protection of information. It
DOES NOT provide information on the selection or acquisition of products that do not provide security functionality or physical security products.
Selecting products without security functions
12.1.3. Agencies selecting products that do not provide a security function or selecting products that will not use their security functions are free to follow their
own agency or departmental acquisition guidelines.
Product specific requirements
12.1.4. Where consumer guides exist for evaluated products, agencies should identify and assess any potential conflicts with this manual. Where further
advice is required, consult the GCSB.
Convergence
151
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents