ISO 27001:

Information Security Management

Information is an all-perva­sive asset that drives opera­tions and processes across all business areas. Today, infor­mation is considered as a key business commodity and is ascribed business value, utili­ty and importance.

Recognizing the business val­ue of information is of extreme importance to all organizations. In summary, business needs to make sure it manages its infor­mation effectively to get the most value out of it.

This means managing informa­tion security risks to ensure that information is not :

  1. denied or made unavailable – e.g. this could be a deni­al of service attack from an external threat, or due to an accidental system failure or overload ;
  2. lost, destroyed or corrupted – e.g. this could be an attack from an external threat, or an accidental system failure or user processing error ; or
  3. leaked, disclosed without authority, or stolen – e.g. this could be an attack from an external threat, an acci­dental system failure, or an insider leaking information to competitors or external colleagues.

Without information security, the business is faced with vari­ous negative impacts including financial consequences, weak­ened protection of the organ­ization’s intellectual capital and IPR, loss of market share, poor productivity and perform­ance ratings, ineffective opera­tions, inability to comply with laws and regulations, or loss of image and reputation.

The stand­ard ISO/IEC 27001:2005, Infor­mation technology – Securi­ty techniques – Information security management systems – Requirements, provides a basis for designing and deploying a management system for infor­mation security.

As a management tool, ISO/IEC 27001 relates to the broad­er roles and responsibilities of an organization such as corpo­rate social responsibility, gov­ernance and legal and regulato­ry obligations. All these aspects can be associated with the increasing dependence of busi­nesses on information systems and information and communi­cation technologies (ICT).

ISO/IEC 27001 is a risk-based specification designed to take care of the information secu­rity aspects of corporate gov­ernance, protection of tangible and non-tangible assets infor­mation assets and legal and contractual obligations, as well as the wide range of threats to the organization’s ICT systems and business processes.

Applying the ISO/IEC 27001 risk management philosophy as part of the business’s over­all risk approach provides the organization with the means to implement effective infor­mation security management in compliance with the organ­ization’s objectives and busi­ness requirements.

ISO 27001:2005

The current family of ISO/IEC 27000 ISMS standards comprises:

  • ISO/IEC 27001 ISMS requirements (published)
  • ISO/IEC 27002 Code of practice for information security management (published

The process of ISMS certification covers following stages
     
Phase One Development and Preparation for an ISMS Certification Audit
The processes that need to be undertaken in establishing your ISMS (Plan Phase) include:

  • Defining ISMS scope & policy (in terms of the nature of the organisation and its business and its assets taking account the business objectives, legal and regulatory requirements and any contractual obligations)
  • •Define risk assessment approach
  • •Identify, assess and evaluate risks
  • •Identify and evaluate options for treating risks
  • •Select control objective and controls (these should be justified on the basis of the risk assessment and conclusions of the risk treatment process)
  • •Produce a Statement of Applicability (SoA) (a document describing the controls that are relevant and applicable to your organisation's ISMS based on the results of the risk assessment and conclusions of the risk treatment process).

After establishing the design goals for your ISMS the next step is to implement and then use the ISMS in your business (Do Phase).  This involves applying the ISMS policies, procedures and any technical controls you produced and implemented as well providing adequate training to users, making sure the security roles and responsibilities have been allocated and understood, and that you have an incident handling process in place for detecting and reacting to security incidents. 
You should also have processes in place for monitoring and reviewing the ISMS and processes for maintaining improving the ISMS as and when necessary (to support the Check and Act Phases).

Before going for certification your ISMS should have been operational for a period of time to ensure it is functioning properly, users are trained and that your  ISMS documentation and record systems are fully functional and operating correctly.  Once you are satisfied that your ISMS is running according your design specification then you should contact one of the certification bodies that have been accredited to carry out ISO/IEC 27001 certification audits.  You then go into the Phase Two mentioned below.

Phase Two Certification Audit Process
The second phase involves employing one of the accredited certification bodies to carry out an audit of your ISMS.  The audit itself involves an initial discussion with the certification body regarding certification requirements; then a review of your ISMS documentation (Stage 1 Audit) is followed by a visit to your ISMS site(s) (Stage 2 Audit). 

During the Stage 1 part of the audit, the CB obtains documentation from the organisation about the design of the ISMS covering at least the organisation's information security risk assessment, the Statement of Applicability, and the core elements of the ISMS.  The objectives of this stage are to provide a focus for planning the Stage 2 Audit by gaining an understanding of the ISMS in the context of the organisation's security policy and objectives, and, in particular, of the organisation's state of preparedness for the audit. 

The objectives of the (stage 2) audit  are to confirm that the organisation adheres to its own policies, objectives and procedures and that ISMS conforms with all the requirements of the ISMS standard or normative document and is achieving the organisation’s policy objectives.  To do this, the Certification Body’s audit team is likely to focus on the:

  • Assessment of information security related risks and the resulting design of the ISMS
  • The Statement of Applicability
  • Objectives and targets derived from this process
  • Performance monitoring, measuring, reporting and reviewing against the objectives and targets
  • Security and management reviews
  • Management responsibility for the information security policy
  • Links between policy, the results of information security risk assessments, objectives and targets, responsibilities, programmes, procedures, performance data, and security reviews.

Phase Three Follow-up Management Activities
The certificate that is awarded will last for three years after which the ISMS needs to be re-certified.  Therefore there is a third phase of the process (assuming the certification has been successful and a certificate has been issued), which involves the certification body visiting your ISMS site on a regular basis (e.g. every 6-9 months) to carry out a surveillance audit.  This type of surveillance visit carries on throughout the three-year period.  The purpose of these surveillance and reassessment visits is to verify that the information security management system (ISMS) is still compliant with the requirements of ISO/IEC 27001and that the ISMS has been properly implemented and maintained: is the scope of the ISMS still valid, is the security provided still effective, is there an appropriate monitoring and improvement programme in place, etc. 

Unique features of ISO 14001
  • Comprehensive: all members of the organization participate in environmental protection, the EMS considers all stakeholders, and there are processes to identify all environmental impacts.
  • Proactive: it focuses on forward thinking and action instead of reacting to command and control policies.
  • Systems approach: it stresses on improving environmental protection by using a single environmental management system across all functions of the organization.
  • Continual improvement: of processes based on objective measurement

Benefits

Many leading companies have discovered the business benefits that can be achieved through ISMS. Below are examples of some of the advantages that your company might experience:

  • Assurance through discipline of compliance
  • Risk management
  • Secure environment (Protection of IPRs)
  • Minimize security breaches (continuity of business)
  • Increase trust & customer confidence & business opportunities

Overview of ISO 27001:2005 ISMS

The ISO IEC 27001 2005 standard is an information security management standard. It defines a set of information security management requirements. These information security requirements are listed in sections 4 to 8. Therefore, the following information starts with section 4.

4. ESTABLISH YOUR ORGANIZATION’S ISMS

4.1 STUDY GENERAL ISMS REQUIREMENTS

  • Define your organization’s ISMS.
  • Implement your organization’s ISMS.
  • Operate your organization’s ISMS.
  • Monitor your organization’s ISMS.
  • Review your organization’s ISMS.
  • Maintain your organization’s ISMS.
  • Improve your organization’s ISMS.
  • Document your organization’s ISMS.

4.2 DEVELOP YOUR ORGANIZATION’S ISMS

4.2.1 DEFINE AND PLAN YOUR ISMS

  • Define the scope and boundaries of your ISMS.
  • Define your organization’s ISMS policy.
  • Define your approach to risk assessment.
  • Identify your organization’s security risks.
  • Analyze and evaluate your organization’s security risks.
  • Identify and evaluate risk treatment options and actions.
  • Select control objectives and controls to treat risks.
  • Make sure that management formally approves all
    residual risks (those that are left over after you’ve implemented your risk treatment decisions).
  • Get authorization from management before you implement and operate your organization’s ISMS.
  • Prepare a Statement of Applicability that lists your organization’s specific control objectives and controls.

4.2.2 IMPLEMENT AND OPERATE YOUR ISMS

  • Develop a risk treatment plan to manage your organization’s information security risks.
  • Implement your organization’s risk treatment plan.
  • Implement your organization’s security controls.
  • Implement your organization’s educational programs.
  • Manage and operate your organization’s ISMS.
  • Manage your organization’s ISMS resources.
  • Implement your organization’s security procedures.

4.2.3 MONITOR AND REVIEW YOUR ISMS

  • Use procedures and controls to monitor your ISMS.
  • Use procedures and controls to review your ISMS.
  • Perform regular reviews of your ISMS.
  • Verify that your security requirements are being met.
  • Review your risk assessments on a regular basis.
  • Review your residual risks on a regular basis.
  • Review acceptable levels of risk on a regular basis.
  • Perform regular internal audits of your ISMS.
  • Perform regular management reviews of your ISMS.
  • Update your information security plans.
  • Maintain a record of ISMS events and actions.

4.2.4 MAINTAIN AND IMPROVE YOUR ISMS

  • Implement your ISMS improvements.
  • Take appropriate corrective actions.
  • Take appropriate preventive actions.
  • Apply the security lessons that you have learned.
  • Communicate ISMS changes to all interested parties.
  • Make sure that your organization’s ISMS changes
    achieve the intended objectives.

4.3 DOCUMENT YOUR ORGANIZATION’S ISMS

4.3.1 DEVELOP ISMS DOCUMENTS AND RECORDS

  • Establish records that document decisions.
  • Document your organization’s ISMS.

4.3.2 CONTROL YOUR ISMS DOCUMENTS

  • Protect and control your ISMS documents.
  • Establish a procedure to control ISMS documents.

4.3.3 CONTROL YOUR ISMS RECORDS

  • Establish records for your organization’s ISMS.
  • Maintain records for your organization’s ISMS.

5. MANAGE YOUR ORGANIZATION’S ISMS

5.1 SHOW THAT YOU SUPPORT YOUR ISMS

  • Demonstrate that your management supports the establishment of an ISMS.
  • Demonstrate that your management supports the implementation of an ISMS.
  • Demonstrate that your management supports the operation of your ISMS.
  • Demonstrate that your management supports the monitoring of your ISMS.
  • Demonstrate that your management supports the review of your ISMS.
  • Demonstrate that your management supports the maintenance of your ISMS.
  • Demonstrate that your management supports the improvement of your ISMS.

5.2 MANAGE YOUR ISMS RESOURCES

5.2.1 PROVIDE RESOURCES FOR YOUR ISMS

  • Identify your organization’s ISMS resource needs.
  • Provide the resources that your ISMS needs.
  • Identify the resources that will be needed in order to ensure that your organization’s information security procedures support its business requirements.
  • Identify the resources needed to meet your organization’s legal security requirements.
  • Identify the resources needed to meet your organization’s regulatory security requirements.
  • Identify the resources needed to meet your organization’s contractual security obligations.
  • Identify the resources needed to ensure that all implemented security controls are correctly applied.
  • Identify the resources needed to ensure that ISMS management reviews are routinely carried out.
  • Identify the resources needed to ensure that you will be able to react appropriately to the results of your ISMS management reviews.
  • Identify the resources needed to ensure that you will be able to improve the effectiveness of your ISMS when required to do so.

5.2.2 ENSURE THAT ISMS PERSONNEL ARE COMPETENT

  • Ensure that all ISMS personnel are competent and can perform the tasks that are assigned to them.
  • Evaluate the effectiveness of your organization’s ISMS personnel training and employment activities.
  • Maintain records that document the competence of personnel performing work that affects your ISMS.
  • Make your personnel aware of how important their information security activities are.

ISO IEC 27001 IN PLAIN ENGLISH

6. AUDIT YOUR ORGANIZATION’S ISMS

ESTABLISH AN INTERNAL AUDIT PROCEDURE

  • Establish an internal ISMS audit procedure.
  • Document your internal ISMS audit procedure.

PLAN YOUR INTERNAL AUDITS

  • Plan your internal ISMS audit projects and activities.
    • Figure out how often internal audits should be done.
    • Schedule your internal audits at planned intervals.
    • Clarify the scope of each internal ISMS audit.
    • Specify the audit criteria for each internal audit.
    • Define your internal ISMS audit methods.
    • Select your internal ISMS auditors.

CONDUCT INTERNAL AUDITS

  • Carry out regular internal ISMS audits.
    • Audit your organization’s ISMS control objectives.
    • Audit your organization’s ISMS controls.
    • Audit your organization’s ISMS processes.
    • Audit your organization’s ISMS procedures.

TAKE REMEDIAL ACTION

  • Eliminate nonconformities and their causes.
  • Take follow up actions to ensure that nonconformities
    and causes have been eliminated without undue delay.
    • Verify that remedial actions have actually been taken.
    • Report the results of your verification activities.

 

7. REVIEW YOUR ORGANIZATION’S ISMS

7.1 PERFORM MANAGEMENT REVIEWS

  • Carry out management reviews of your ISMS.
    • Make sure that your organization’s management
      people review your ISMS at planned intervals.
  • Examine the performance of your ISMS.
    • Examine the ongoing suitability of your ISMS.
    • Examine the ongoing adequacy of your ISMS.
    • Examine the ongoing effectiveness of your ISMS.
  • Assess whether or not your organization’s ISMS should be changed or improved.
    • Assess whether or not your information security policy should be changed or improved.
    • Assess whether or not your information security objectives should be changed or improved.
  • Keep a record of your ISMS management reviews.
    • Record the results of ISMS management reviews.

7.2 EXAMINE MANAGEMENT REVIEW INPUTS

  • Examine information about your ISMS (inputs).
    • Examine the results of prior management reviews.
    • Examine the results of previous ISMS audits.
    • Examine previous ISMS measurement results.
    • Examine the status of previous remedial actions.
    • Examine security issues that were inadequately
      addressed during the previous risk assessment.
    • Examine opportunities to improve your ISMS.
    • Examine changes that might affect your ISMS.

7.3 GENERATE MANAGEMENT REVIEW OUTPUTS

  • Generate decisions and actions (outputs).
    • Generate management review decisions and actions to improve your organization’s ISMS.
    • Generate management review decisions and actions to update your organization’s ISMS.
    • Generate management review decisions and actions to respond to events that affect the ISMS.
    • Generate management review decisions and actions to address your ISMS resource needs.

ISO IEC 27001 IN PLAIN ENGLISH

8. IMPROVE YOUR ORGANIZATION’S ISMS

8.1 CONTINUALLY IMPROVE YOUR ISMS

  • Improve the effectiveness of your ISMS.
    • Use your security policy to continually improve the effectiveness of your ISMS.
    • Use your security objectives to continually improve the effectiveness of your ISMS.
    • Use your security audit results to continually improve the effectiveness of your ISMS.
    • Use your management reviews to continually improve the effectiveness of your ISMS.
    • Use your corrective actions to continually improve the effectiveness of your ISMS.
    • Use your preventive actions to continually improve the effectiveness of your ISMS.
    • Use your monitoring process to continually improve the effectiveness of your ISMS.

8.2 CORRECT ACTUAL ISMS NONCONFORMITIES

  • Establish a corrective action procedure to prevent the recurrence of actual nonconformities.
    • Make sure that your corrective action procedure expects you to identify actual nonconformities.
    • Make sure that your corrective action procedure expects you to identify the causes of your nonconformities.
    • Make sure that your procedure expects you to evaluate whether you need to take action.
    • Make sure that your procedure expects you to develop corrective actions when they are needed.
    • Make sure that your procedure expects you to prevent the recurrence of actual nonconformities.
    • Make sure that your corrective action procedure expects you to eliminate the causes of your
      organization’s nonconformities.
    • Make sure that your procedure expects you to record the results of any corrective actions taken.
    • Make sure that your procedure expects you to review the results of any corrective actions taken.
  • Document your corrective action procedure.
  • Implement your corrective action procedure.
    • Use your organization’s corrective action procedure to identify nonconformities.
    • Use your organization’s corrective action procedure to identify causes.
    • Use your procedure to evaluate whether or not you need to take corrective action.
    • Use your procedure to develop corrective actions whenever corrective actions are actually needed.
    • Use your procedure to take corrective actions.
    • Use your procedure to prevent the recurrence of actual nonconformities.
    • Use your procedure to eliminate the causes of actual nonconformities.
    • Use your procedure to record the results of any corrective actions taken.
    • Use your procedure to review the corrective actions that have been taken.
  • Maintain your corrective action procedure.

8.3 PREVENT POTENTIAL ISMS NONCONFORMITIES

  • Establish a preventive action procedure to prevent the occurrence of potential nonconformities.
    • Make sure that your preventive action procedure expects you to identify potential nonconformities.
    • Make sure that your procedure expects you to identify the causes of potential nonconformities.
    • Make sure that your procedure expects you to evaluate whether or not your organization needs to take preventive action.
    • Make sure that your procedure expects you to develop preventive actions when they are needed.
    • Make sure that your procedure expects you to prevent the occurrence of potential nonconformities.
    • Make sure that your procedure expects you to eliminate the causes of potential nonconformities.
    • Make sure that your procedure expects you to record the results of any preventive actions taken.
    • Make sure that your procedure expects you to review the results of any preventive actions taken.
  • Document your preventive action procedure.
  • Implement your preventive action procedure.
    • Use your organization’s preventive action procedure to identify potential nonconformities.
    • Use your preventive action procedure to identify the causes of potential nonconformities.
    • Use your preventive action procedure to evaluate whether or not you need to take preventive action.
    • Use your preventive action procedure to develop preventive actions whenever they are needed.
    • Use your procedure to take preventive actions.
    • Use your preventive action procedure to prevent the occurrence of potential nonconformities.
    • Use your preventive action procedure to eliminate the causes of potential nonconformities.
    • Use your preventive action procedure to record the results of any preventive actions taken.
    • Use your preventive action procedure to review the preventive actions that have been taken.
  • Maintain your preventive action procedure.

 

 

FAQ (ISO 27001)

CERTIFICATION

If an organisation says they are compliant with ISO/IEC 27002 does this mean they have been certified?
NO. 
ISO/IEC 27002 is not a certification standard.
The only standard that can used for certification is ISO/IEC 27001.

Who is allowed to undertake ISO/IEC 27001 certification audits and award certificates?
Certification audits are carried out by an accredited certification body.
To become accredited the certification body needs to be assessed by a national accreditation body examples being UKAS (UK), SWEDAC (Sweden), KBA (South Korea), JIPDEC or JAB (Japan) and RBA (USA).
Certificates awarded by the certification upon successful completion of a certification audit.

How long is a ISO/IEC 27001 certificate valid for?
An accredited certificate is valid for three years after which the organisation can choose to have its ISMS re-certified.
During the three year period the certification body will under take a number of surveillance audits to check that the ISMS is being maintain and updated to an effective level of information security.

Are ISO/IEC 27001 and ISO/IEC 27002 IT security Standards?
NO they are both information security standards.

What does ISO/IEC 27001 cover?
This standard covers the processes needed to establish, implement and deploy, monitor and review, and maintain and improve an ISMS.
It covers processes such as risk assessment, risk treatment, selection of information security controls, monitoring activities, management reviews, measuring the effectiveness of information security, incident handing process, corrective and preventive activities.
An Annex (A) contains a range of controls that can be selected to manage the risks identified through the risk assessment and treatment processes.

What does ISO/IEC 27002 cover?
This standard is a code of practice which means it contains a set of best practice controls that are used throughout the business world. In addition to defining the control it also provides implementation guidance regarding the control. The controls given in ISO/IEC 27002 are expressed in terms of “should” statements which makes them non-compliant statements.  Whereas the controls in Annex A of ISO/IEC 27001, which are the same set of controls, are expressed in terms of “shall” statements which makes them formal compliance statements which is why this standard can be used for certification purposes.

Can an organisation get a certificate by just implementing the controls in ISO/IEC 27001?
NO 
An organisation needs to have implemented all the requirements specified in ISO/IEC 27001 relating to the processes defined in this standard.  So, for example, they must have undertaken a risk assessment in order to decide which controls they should select from Annex A.

Can ISO/IEC 27001 and ISO/IEC 27002 be used by small businesses?
YES. 
These standards are very flexible to suit all business needs irrespective of size of business or the nature of the business.

Can ISO/IEC 27001 and ISO/IEC 27002 be used by all types of organisation: commercial, government s and not-for-profit?
YES. 
There are many examples of organisations in all these categories that have been certified.