ISO 27002:2022, Control 8.5 – Secure Authentication

ISO 27002:2022 Revised Controls

Book a demo

people,working,in,modern,office.,group,of,young,programmers,sitting

Purpose of Control 8.5

Secure authentication is the primary method which human and non-human users engage with when attempting to utilise an organisation’s ICT assets.

Over the past decade, authentication technology has undergone a fundamental shift from traditional username/password-based validations into a variety of complementing techniques involving biometric information, logical and physical access controls, external device authentications, SMS codes and one time passwords (OTP).

27002:2022-8.5 puts all of this into context and advises organisations on precisely how they should be controlling access to their ICT systems and assets via a secure login gateway.

Control 8.5 is a preventative control that maintains risk by implementing technology and establishing topic-specific secure authentication procedures that ensure human and non-human users and identities undergo a robust and secure authentication procedure when attempting to access ICT resources.

Attributes Table

Control Type Information Security PropertiesCybersecurity ConceptsOperational Capabilities Security Domains
#Preventive#Confidentiality
#Integrity
#Availability
#Protect #Identity and Access Management#Protection
Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

Ownership of Control 8.5

Control 8.5 deals with an organisation’s ability to control access to its network (and the information and data contained within) at critical junctions, such as a login gateway.

Whilst the control does deal with information and data security as a broader concept, the operational guidance is primarily of a technical nature.

As such, ownership should reside with the Head of IT (or organisational equivalent), who holds responsibility for the organisation’s day-to-day IT administration functions.

General Guidance on Control 8.5

Control 8.5 asks organisations to consider authentication controls that are relevant to the type and sensitivity of the data and network that’s being accessed, including:

  • Multi-factor authentication (MFA)
  • Digital certificates
  • Smart access controls (smart cards)
  • Biometric logins
  • Secure tokens

The overriding goal of an organisation’s secure authentication controls should be to prevent and/or minimise the risk of unauthorised access to its protected systems.

To achieve this, Control 8.5 outlines 12 main guidance points. Organisations should:

  1. Restrict the display of information until after a successful authentication attempt.
  2. Display a warning pre-logon which clearly states that information should only be accessed by authorised users.
  3. Minimise the assistance it provides to unauthenticated users who are attempting to access the system e.g. organisations should not divulge which specific part of a login attempt is incorrect, such as a biometric aspect of an MFA login, and instead simply state that the login attempt has failed.
  4. Validate the login attempt only when all required information has been provided to the login service, to maintain security.
  5. Implement industry-standard security measures that protect against blanket access and/or brute force attacks on login portals. These measures can include:
    • CAPTCHA controls
    • Enforcing a password reset after a set amount of failed login attempts
    • Preventing further login attempts following a predefined number of failed attempts

  6. Recording all failed login attempts for auditing and security purposes, including their use in criminal and/or regulatory proceedings.
  7. Initiating a security incident whenever a major login discrepancy is detected, such as a perceived intrusion. In these cases, all relevant internal personnel should be notified, particularly those with systems administrator access or any ability to combat malicious login attempts.
  8. Upon validating a login, relay certain pieces of information to a separate data source that list:
    • The date and time of the previous successful logon
    • A list of all login attempts since the last validated logon

  9. Display passwords as asterisk’s (or similarly abstract symbols), where there is no pressing need not to do so (e.g. user accessibility).
  10. Strictly prohibit the sharing of or display of passwords as clear, legible text.
  11. Maintain a policy of terminating dormant login sessions after a specific period of time. This is particularly relevant for sessions that are active in high risk locations (remote working environments) or on user-supplied assets such as personal laptops or mobile phones.
  12. Limiting the amount of time that an authenticated session can remain open – even when active – relative to the information that’s being accessed (i.e. business critical information or financially sensitive applications).

See how we can help you

Book a tailored hands-on session
based on your needs and goals
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

Guidance – Biometric Logins

ISO recommends that due to a number of factors related to the effectiveness and integrity of biometric login processes over traditional measures (passwords, MFA, tokens etc.), biometric authentication methods should not be used in isolation, and accompanied by at least one other login technique.

Changes and Differences from ISO 27002:2013

27002:2022-8.5 replaces 27002:2014-9.4.2 (Secure log-on procedures).

27002:2022-8.5 contains the same 12 guidance points as its 2013 counterpart, with minor adjustments to the wording, and follows the same set of underlying security principles.

In-line with the rise of MFA and biometric login technologies over the past decade, 27002:2022-8.5 contains explicit guidance on the use of both techniques that organisations should consider when formulating their own set of login controls.

How ISMS.online Helps

Our cloud-based platform provides you with a robust framework of information security controls so that you can checklist your ISMS process as you go to ensure that it meets the requirements for ISO 27000k. Used properly, ISMS. online can assist you in achieving certification with the bare minimum of time and resources.

Get in touch today to book a demo.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

New Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.7NewThreat intelligence
5.23NewInformation security for use of cloud services
5.30NewICT readiness for business continuity
7.4NewPhysical security monitoring
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.16NewMonitoring activities
8.23NewWeb filtering
8.28NewSecure coding

Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures

People Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
6.107.1.1Screening
6.207.1.2Terms and conditions of employment
6.307.2.2Information security awareness, education and training
6.407.2.3Disciplinary process
6.507.3.1Responsibilities after termination or change of employment
6.613.2.4Confidentiality or non-disclosure agreements
6.706.2.2Remote working
6.816.1.2, 16.1.3Information security event reporting

Physical Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
7.111.1.1Physical security perimeters
7.211.1.2, 11.1.6Physical entry
7.311.1.3Securing offices, rooms and facilities
7.4NewPhysical security monitoring
7.511.1.4Protecting against physical and environmental threats
7.611.1.5Working in secure areas
7.711.2.9Clear desk and clear screen
7.811.2.1Equipment siting and protection
7.911.2.6Security of assets off-premises
7.1008.3.1, 08.3.2, 08.3.3, 11.2.5Storage media
7.1111.2.2Supporting utilities
7.1211.2.3Cabling security
7.1311.2.4Equipment maintenance
7.1411.2.7Secure disposal or re-use of equipment

Technological Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
8.106.2.1, 11.2.8User endpoint devices
8.209.2.3Privileged access rights
8.309.4.1Information access restriction
8.409.4.5Access to source code
8.509.4.2Secure authentication
8.612.1.3Capacity management
8.712.2.1Protection against malware
8.812.6.1, 18.2.3Management of technical vulnerabilities
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.1312.3.1Information backup
8.1417.2.1Redundancy of information processing facilities
8.1512.4.1, 12.4.2, 12.4.3Logging
8.16NewMonitoring activities
8.1712.4.4Clock synchronization
8.1809.4.4Use of privileged utility programs
8.1912.5.1, 12.6.2Installation of software on operational systems
8.2013.1.1Networks security
8.2113.1.2Security of network services
8.2213.1.3Segregation of networks
8.23NewWeb filtering
8.2410.1.1, 10.1.2Use of cryptography
8.2514.2.1Secure development life cycle
8.2614.1.2, 14.1.3Application security requirements
8.2714.2.5Secure system architecture and engineering principles
8.28NewSecure coding
8.2914.2.8, 14.2.9Security testing in development and acceptance
8.3014.2.7Outsourced development
8.3112.1.4, 14.2.6Separation of development, test and production environments
8.3212.1.2, 14.2.2, 14.2.3, 14.2.4Change management
8.3314.3.1Test information
8.3412.7.1Protection of information systems during audit testing
Trusted by companies everywhere
  • Simple and easy to use
  • Designed for ISO 27001 success
  • Saves you time and money
Book your demo
img

Streamline your workflow with our new Jira integration! Learn more here.