This risk assessment MUST be the basis of a security architecture design. 11.7.30. Security Architecture 11.7.30.R.01. Rationale The foundation of strong security architecture in RFID follows these important principles: 1. Physical Security - over readers, secure areas, issued and unissued access cards; 2. Controlled access to the data – only authorised entities (people, systems, devices) can read and write information to the cards, card databases and backend systems; 3. Control over access to the system – only authorised entities can configure or add devices to the system, and all devices on the system are authentic and trustworthy; 4. Confidence and trust – back-end systems are designed and implemented in accordance with the current version of the NZISM. This includes intrusion detection and incident management mechanisms and procedures. 11.7.30.R.02. Rationale Some access systems may cover several organisations or sites. In such cases, multiple organisations or sites may require access to databases that contain personnel identifiers, passwords and access permissions. The security architecture should incorporate strong security controls including the authentication of external entities, incident management, audit logging and other essential security controls. 11.7.30.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:3138] Agencies MUST develop a strong security architecture to protect access to databases and systems. 11.7.30.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3139] Agencies SHOULD apply the NZISM access controls (Chapter 11) and cryptographic controls (Chapter 17) to access card systems. 11.7.30.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3141] Agencies SHOULD consider the application of the following design elements: Implement a Demilitarized Zone (DMZ) to isolate card systems from other parts of the organisation’s network and from high-risk Internet Protocol (IP) network connections; Secure or remove connections between the Internet and card system network segments; Secure or remove vulnerable dialup modem links; Secure or remove vulnerable wireless radio links and network access points; and Network activity monitoring for unusual or anomalous access activity and well as intrusion detection. 11.7.31. Policy 11.7.31.R.01. Rationale An Access Card Usage Policy is an essential component addressing topics such as how personal information is stored and shared, card holder responsibilities and procedures to manage card loss or damage. Refer also to Chapter 20 – Data Management. 11.7.31.R.02. Rationale Any access card implementation should also be incorporated into the agency’s security policies. Refer also toChapter 5 – Information Security Documentation. 11.7.31.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3156] Agencies SHOULD develop, implement and maintain an Access Card Usage Policy. 11.7.31.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3157] Agencies SHOULD incorporate access cards into the agency’s security policies and information security documentation. 11.7.32. Physical Security 11.7.32.R.01. Rationale Physical security over readers, door controls, cables and control systems, as well as the cards themselves is fundamental to the operation of a secure system. 11.7.32.R.02. Rationale In order to minimise unnecessary electromagnetic radiation readers and control equipment should be carefully positioned. Care should be taken with the use of card readers in proximity to: Fuel, ordnance, and other hazardous materials, Metal and reflective objects that can modify and amplify signals in unintended and potentially harmful ways, and Legitimate radio systems to avoid interference. 11.7.32.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3162] Agencies SHOULD select systems that provide resistance to physical or electronic tampering. 11.7.32.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3163] Agencies SHOULD implement systems to minimise the risk of physical or electronic tampering. 11.7.32.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD 150 [CID:3165] Version_3.5__January-2022

Select target paragraph3

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