Iso 27001
Iso 27001
Iso 27001
BY BOBBY SHARON
WHY ISO 27001
ISO 27001 is the global standard for effective information management. It helps organizations avoid potentially
costly security breaches. ISO 27001-certified organizations can show customers, partners and shareholders that
they have taken steps to protect data in the event of a breach.
IT (61 Controls) A.9, A.10, A.12, A.13, A.14, A.16, A.17
Objective:
• To ensure that policies regarding information security are written in accordance with your organization's
requirements.
5.1 Management direction for Management direction for Does management provide direction and support for information security in
information security information security accordance with business requirements and relevant laws and regulations?
Is there an information security policy document, or set of policies, that has been
defined, approved by management, and has it been published and communicated to all
Management direction for Policies for information employees and relevant external parties?
5.1.1 information security security
Does it contain objectives, define infosec, assign roles and point to a "process for
handling deviations and exceptions"?
Is there a procedure for the information security policy, or policies, to be reviewed at
Management direction for Review of the policies for planned intervals or if significant changes occur, and does this process ensure its
5.1.2
information security information security continuing suitability, adequacy, and effectiveness, and is there evidence that the policy
(or policies) is applied?
Objective:
• To establish a management framework and assign information security roles for how the controls will be
implemented.
• To adopt security guidelines for when employees access, process and store information while working out-of-
office.
Objective:
• To ensure that all parties (employees and contractors) understand their requirements and responsibilities before,
during and after their term of employment.
• This involves conducting background checks, adhering to information security policies, conducting necessary
training and implementing a formal disciplinary process in order to protect the organisation’s interests.
Does the organization conduct background verification checks on all candidates for employment,
Prior to in accordance with relevant laws, regulations and ethics, and are these checks sufficient
7.1.1 employment Screening considering the business requirements, the classification of the information to be accessed and
the related risks?
Do contractual agreements with employees and contractors state their and the organization's
7.1.2 Prior to Terms and conditions of responsibilities for information security? e.g. confidentiality agreement, respecting information
employment employment classification requirements, responsibilities when handling 3rd party information, obligations
beyond termination?
Does the organization conduct background verification checks on all candidates for employment,
Prior to in accordance with relevant laws, regulations and ethics, and are these checks sufficient
7.1.1 employment Screening considering the business requirements, the classification of the information to be accessed and
the related risks?
Do contractual agreements with employees and contractors state their and the organization's
7.1.2 Prior to Terms and conditions of responsibilities for information security? e.g. confidentiality agreement, respecting information
employment employment classification requirements, responsibilities when handling 3rd party information, obligations
beyond termination?
Does the organization define and enforce information security responsibilities and duties that
Termination and Termination or change of remain valid after termination or change of employment, and are these communicated to the
7.3.1 change of employment responsibilities employee or contractor? For example, continuing contractual clauses beyond termination (e.g.
employment
confidentiality) and how an internal move should be considered as a termination and re-hiring.
Objective:
• To identify, classify and prevent the disclosure of information and assets.
• This involves defining acceptable use, implementing a classification scheme, outlining procedures for handling
assets and implementing procedures to securely dispose of media.
Does the organization classify information? Do classification levels consider legal requirements,
Information value, criticality and sensitivity to unauthorized disclosure or modification?
8.2.1 classification Classification of information The "value" should be built into the classification levels which should be incremental, e.g. in
terms of confidentiality, integrity and availability requirements.
Information Has an appropriate set of procedures been developed and implemented for information labelling
8.2.2 classification Labelling of information in accordance with the information classification scheme?
Has the organization developed and implemented procedures for handling assets in accordance
Information
8.2.3 Handling of assets with the information classification scheme? For example covering access restrictions, transfer
classification methods, storage location or media for each level of classification.
Management of removable Are there procedures for the management of removable media in accordance with the
8.3.1 Media handling media classification scheme?
8.3.2 Media handling Disposal of media Are there formal procedures for the disposal of media securely when no longer required?
Are there procedures to protect media containing information against unauthorized access,
8.3.3 Media handling Physical media transfer misuse or corruption during transportation?
Objective:
• To limit access to and prevent unauthorized access of information, and hold individuals accountable for protecting
authentication information (such as PINs and passwords).
• This involves implementing an access control policy, controlling access rights, defining the use of secret
authentication information and restricting any programs with override capabilities.
Business Is there an established, documented and reviewed access control policy based on business and
9.1.1 requirements of Access control policy information security requirements?
access control
Business Access to networks and Are users restricted to access only those networks and network services that they have been
9.1.2 requirements of
access control network services specifically authorised to use?
Is there a formal user registration and de-registration process to enable assignment of access
User access User registration and de- rights?
9.2.1 management registration Does it ensure only unique user IDs are used to enable users to be linked to and held responsible
for their actions? Are leavers' user IDs immediately disabled or removed?
User access Is there a formal user access provisioning process to assign or revoke access rights for all user
9.2.2 management User access provisioning types to all systems and services?
User access Management of privileged
9.2.3 Is the allocation and use of privileged access rights restricted and controlled?
management access rights
Is there a formal management process to control the allocation of secret authentication
User access Management of secret information? [Passwords are a commonly used type of secret authentication information and are
9.2.4 management authentication information of a common means of verifying a user’s identity. Other types of secret authentication information
users are cryptographic keys and other data stored on hardware tokens (e.g. smart cards) that produce
authentication codes.]
9.2.5 User access Review of user access rights Do asset owners review users' access rights at regular intervals? Does it consider both access and
management permissions?
User access Removal or adjustment of Are access rights of employees and external party users to information and processing facilities
9.2.6
management access rights removed upon termination (or change) of their employment, contract or agreement?
System and
Is access to information and application system functions restricted in accordance with the access
9.4.1 application access Information access restriction
control policy?
control
System and
Is there a secure log-on procedure to control access to systems and applications where required
9.4.2 application access Secure log-on procedures
control by the access control policy?
System and
9.4.3 application access Password management system Are the password management systems interactive and do they ensure quality passwords?
control
System and Use of privileged utility Are there quidelines for the use of utility programs that might be capable of overriding system
9.4.4 application access
control programs and application controls? Are their use restricted and tightly controlled?
System and Access control to program Is access to program source code restricted? Is access to associated items (such as designs,
9.4.5 application access
control source code specifications, verification plans and validation plans) restricted?
Objective:
• To ensure encryption and key management is used to maintain the confidentiality, integrity and authenticity of
important information.
• This involves outlining, through a cryptographic policy, the use and validity period of cryptographic keys.
Cryptographic Policy on the use of Has a policy on the use of cryptographic controls for protection of information been developed
10.1.1 controls cryptographic controls and implemented?
Cryptographic
10.1.2 Key management Has a policy on the management of cryptographic keys been developed and implemented?
controls
Objective:
• To prevent unauthorized access to information that may cause loss or interruption to operations.
• To prevent the compromise of assets through loss, damage or theft.
• This involves defining and implementing a physical security perimeter, securing areas involved in transport (such
as loading bays), regularly servicing equipment and protecting equipment when taken off office premises.
11.2.9 Equipment Clear desk and clear screen Is there a clear desk policy for papers and removable storage media, and a clear screen policy for
policy information processing facilities?
Objective:
• To ensure the integrity of information processing facilities and operational systems, protecting these facilities from
malware, preventing the loss of data, maintaining consistency across activity logs, mitigating potential technical
risks and minimizing disruptions brought on by audit activities.
• This involves documenting operating procedures (such as changes to organizational processes), separating
operational environments, implementing anti-malware software and making users aware of what constitutes
acceptable use, following an agreed backup policy, monitoring software installation and regularly evaluating risks.
12.2.1 Protection from Controls against malware Are there detection, prevention and recovery controls in place to protect against malware? Is this
malware combined with appropriate user awareness education/training?
12.3 Backup Backup Does the organisation protect against loss of data?
Is there an agreed backup policy, and are backup copies of information, software and system
12.3.1 Backup Information backup images taken and tested regularly in accordance with this policy? Are backups included in the
retention policy?
12.4.1 Logging and Event logging Are required event logs identified, produced, kept and regularly reviewed or alerts configured?
monitoring Do they record user activities, exceptions, faults and information security events?
Logging and
12.4.2 monitoring Protection of log information Are logging facilities and log information protected against tampering and unauthorised access?
Are system administrator and system operator activities logged, and are the logs protected and
Logging and Administrator and operator regularly reviewed?
12.4.3 monitoring logs
Privileged user account holders may be able to manipulate the logs under their control, therefore
it is crucial to protect and review the logs to maintain accountability for privileged users.
12.4.4 Logging and Clock synchronisation Are the clocks of all relevant information processing systems within an organization or security
monitoring domain synchronized with a single reference time source?
12.5.1 Control of operational Installation of software Are procedures implemented to control the installation of software on operational systems?
software on operational systems
Technical vulnerability Technical vulnerability
12.6 management management Does the organisation prevent the exploitation of technical vulnerabilities?
Is timely information about technical vulnerabilities of information systems being used obtained,
Technical vulnerability Management of technical
12.6.1 is the organisation’s exposure to such vulnerabilities evaluated, and are the appropriate measures
management vulnerabilities
taken to address the associated risk?
Technical vulnerability Restrictions on software
12.6.2 Have rules governing the installation of software by users been established and implemented?
management installation
12.7 Information systems Information systems Does the organization minimize the impact of audit activities on operational systems?
audit considerations audit considerations
Information systems Information systems Are audit activities involving verification of operational systems carefully planned and agreed to
12.7.1 audit considerations audit controls minimize disruptions to business processes?
Objective:
• To monitor the internal and external transfer of information.
• This involves implementing information transfer policies across all communication facilities (such as email, social
media and internal messaging platforms).
Objective:
• To ensure that information security requirements are established across the lifecycle of information systems and
included when updating existing systems or implementing new systems.
• To ensure that data being used for testing is only accessed by authorized personnel.
• This involves protecting information that passes through public networks to prevent misrouting, alteration or
unauthorized disclosure, establishing secure development areas and regularly testing security facilities.
14.2.1 Security in development and Secure development policy Are there established rules for the development of software and systems, and are they applied to developments within your
support processes control, i.e. within the organization or sub-contracted?
14.2.2 Security in development and System change control Are there formal change control procedures built within the development lifecycle to control changes to systems ?
support processes procedures
14.2.3 Security in development and Technical review of applications When operating systems are changed, are business critical applications reviewed and tested to ensure there is no adverse impact
support processes after operating platform changes on organisational operations or security?
14.2.4 Security in development and Restrictions on changes to Are modifications to vendor-supplied software packages discouraged, limited to necessary changes and are all changes strictly
support processes software packages controlled?
14.2.5 Security in development and Secure system engineering Have principles for engineering secure systems been established, documented and maintained, and are they applied?
support processes principles
Are development environments for system development and integration efforts in place and appropriately protected? Are they
14.2.6 Security in development and Secure development used throughout the development lifecycle?
support processes environment A secure development environment includes people, processes and technology associated with system development and
integration.
14.2.7 Security in development and Outsourced development Do you supervise and monitor the activity of outsourced system development?
support processes
Is security functionality testing conducted during development? Including the preparation of a detailed schedule of activities and
Security in development and test inputs and expected outputs under a range of conditions. For in-house developments, such tests should initially be performed
14.2.8 support processes System security testing by the development team. Independent acceptance testing should then be undertaken (both for in-house and for outsourced
developments) to ensure that the system works as expected and only as expected. The extent of testing should be in proportion to
the importance and nature of the system.
14.2.9 Security in development and System acceptance criteria Are there acceptance testing programs? Are acceptance criteria been established for new information systems, upgrades and new
support processes versions? Do they include testing of information security requirements?
14.3.1 Test data Protection of test data Is test data selected appropriately? Is it protected and controlled?
Objective:
• To ensure that information security requirements are established across the lifecycle of information systems and
included when updating existing systems or implementing new systems.
• To ensure that data being used for testing is only accessed by authorized personnel.
• This involves protecting information that passes through public networks to prevent misrouting, alteration or
unauthorized disclosure, establishing secure development areas and regularly testing security facilities.
Information security in Information security Are information security requirements for mitigating the risks associated with supplier's access to
15.1.1 policy for supplier
supplier relationships relationships the organization's assets agreed with the supplier and documented?
Addressing security Are all relevant information security requirements established and agreed with each supplier that
Information security in
15.1.2 supplier relationships within supplier may access, process, store, communicate, or provide IT infrastructure for, the organisation's
agreements information?
Information security in Information and Do agreements with suppliers include requirements to address the information security risks
15.1.3 communication
supplier relationships technology supply chain associated with information and communications technology services and product supply chain?
Objective:
• To ensure that any information security incidents are managed effectively and consistently.
• This involves reporting any weaknesses through the appropriate management channels as quickly as possible,
responding to these incidents in line with established procedures and preserving evidence.
Objective:
• To ensure the continuation of information security and that these measures are in line with your organisation's
continuity plans.
• To ensure the availability of information processing facilities.
Objective:
• To avoid information security breaches of a legal, statutory, regulatory or contractual nature, and ensure that
information security is carried out according to organizational requirements
• This involves identifying compliance requirements, protecting against any implications (loss, theft etc)
according to these requirements, ensuring the protection of sensitive information and regularly reviewing the
compliance of information systems.