Multi-Step Authentication 16.7.20. Multi-step Authentication is a design and architectural approach to control access to resources by sequentially using multiple authentication verifiers. Each authentication step grants access to increasingly privileged areas of the system until access to the desired resources is reached (refer also to 16.4 – Privileged Access Management). Multi-Step Authentication can be activated by risk-based “triggers” where risk factors are identified. 16.7.21. Multi-step Authentication may require only one authentication factor or mechanism, so it is important not to confuse Multi-Step Authentication with Multi-Factor Authentication. Multi-Step Authentication may not be as secure as MFA and cannot be an appropriate substitute for MFA. A key risk is repeated use of a single authentication factor. 16.7.22. It is also worth noting, however, that Multi-Step combined with Multi-Factor Authentication is a strong architectural security construct, particularly when separate authentication factors are required at each step when accessing privileged accounts. Perfect Forward Secrecy 16.7.23. In addition to the encryption protocols and algorithms discussed in Chapter 17 - Cryptography, the concept ofPerfect Forward Secrecy (PFS), often simplified to Forward Secrecy, should also be incorporated into any authentication mechanism design. 16.7.24. Forward Secrecy is a property of secure communication protocols that is intended to prevent a compromised encryption key from being used to decrypt previously encrypted traffic. Clearly a compromised key must be immediately replaced in order to maintain the integrity of communications. This mechanism is described as a “rolling secrets” technique and is designed to prevent device spoofing and the cloning of mobile clients. 16.7.25. A “rolling secret” key is located on the client device. The client receives two encrypted packages. The first contains another private key and is decrypted by the current private key held on the client device. The new key is used to decrypt the second package and the new private key replaces the existing private key, which is then discarded. The new key is used to encrypt traffic to the authentication server. With each cycle the client replaces the old key with the new key. Cryptography 16.7.26. The use of encryption is a fundamental component is the security of a Multi-Factor Authentication mechanism. It is essential that only approved cryptographic protocols and algorithms are used, refer to Chapter 17 – Cryptography. Risk Analysis 16.7.27. The design of Multi-Factor Authentication should start with a risk review in order to identify any existing and new risks from changing environments, user populations and threat landscapes. Some early steps will include: Review business drivers, existing identity infrastructure, enterprise applications, core platform infrastructure and development plans for each of these; Ensure any plans for cloud and related services are reviewed and incorporated; Identify authentication use cases including employees and contractors, consumers, customers, partners, and suppliers. For Digital Government this may also include the General Public for some systems; Develop baseline requirements; Undertake a threat analysis for each use case; and Select control mechanisms to manage identified risks. 16.7.28. This risk analysis will inform and direct the development of an authentication architecture to provide robust but usable security for each use case. Some key questions include: How will users access the system or application? At what stage will users be authenticated? What authentication factors will provide the appropriate level of authentication and security? Is the level of authentication appropriate to secure and protect the systems, data and other related assets? and Is there sufficient capacity to service anticipated workloads? Governance and Control 16.7.29. Good governance processes assist in identifying potential risks to your systems, data, employees, partners and contractors and reduces the risk of a breach or failure to comply with legislation and regulation. Good governance processes support the fulfilment of fiduciary duties of senior and executive management. 16.7.30. Technology governance must demonstrate effective control, security, effectiveness and clear accountability. Identity Access Management and Authentication are fundamental components in protecting agency systems, data and technology assets and underpinning technology governance structures. 16.7.31. There are also a number of national and international legislative and regulatory requirements and accepted international standards which may influence aspects of governance, particularly in relation to data protection and privacy. While not an exhaustive list, these include: New Zealand’s Privacy Act; New Zealand’s Public Records Act; The European Union’s Payment Services Directive (PSD); The EU’s General Data Protection Regulation (GDPR); ISO/IEC 27701:2019 - Security techniques. An Extension to ISO/IEC 27001 and ISO 27002 for privacy information management, particularly GDPR; The US Health Insurance Portability and Accountability Act (HIPAA); The Payment Card Industry Data Security Standard (PCI DSS). References 16.7.32. Additional information relating to event logging is contained in: Reference 228 Title Publisher Source Version_3.5__January-2022

Select target paragraph3

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