IS0 27001 is a Model for information security management systems. It is an information security system registration scheme where a company’s information security procedures and processes are assessed to an information security management Standard.  This Standard has been agreed in this country, the European Union and Internationally

27001 is the working standard and it contains 7 main sections

  1. Scope
  2. Normative References
  3. Terms and definitions
  4. Context of the Organisation
  5. Leadership
  6. Planning
  7. Support
  8. Operation
  9. Performance Evaluation
  10. Improvement

Put very simply, ISO 27001 is a declaration of an organisations ability to demonstrate its capability to consistently protect information security and to satisfy its customers’ information security needs.

27002 is the code of practice and it is normal to use this to set up a comprehensive Information Security Management System (ISMS).  There are 15 main sections 4.0 to 18.0:

ISO 27002 BY SECTION

Section 0:  Introduction

Starting from ‘What is information security?’, the introduction explains about information and how to make use of the standard.

Section 1: Scope

The Standard gives information on the extent of cover for an ISMS.

Section 2:  Normative References.

Reference is made to documents that are referenced within 27002 and are indispensable for operation of the Information Security Management System.

Section 3: Terms and Definitions

Including ISO 27000, which is a set of terms and definitions

Section 4:  Structure of the Standard

This page simply explains that the standard contains 14 security control clauses containing a total of 35 main security categories and 113 controls. 

Section 5: Information Security Policies

A set of policies for information security defined, approved by management, published and communicated to employees and relevant external parties.

Management should define a policy to clarify their direction and support for information security, meaning a short, high-level information security policy statement laying down the key information security directives and mandates for the entire organisation.

Normally it will spell out the three main criteria

CIA

C –  Confidentiality
I  –  Integrity
A –  Availability

This is normally supported by a comprehensive set of more detailed corporate information security policies, typically in the form of an information security policy manual. The policy manual in turn is supported by a set of information security procedures and guidelines.

This policy is normally signed by the most senior person and displayed.

Section 6: Organisation of Information Security

A management framework should be designed and implemented to initiate and control the implementation of information security within the organisation. Responsibilities for information security risk management and in particular for acceptance of residual risks.

A Forum, made up of a cross section of people in the organisation should meet regularly.

6.1 Information Security Roles and Responsibilities

The organisation should have a management structure for information security. Senior management should provide direction and commit their support, for example by approving information security policies. Roles and responsibilities should be defined for the information security function. Other relevant functions should cooperate and coordinate their activities. IT facilities should be authorised.

Confidentiality agreements should reflect the organisation’s needs. Contacts should be established with relevant authorities (e.g. law enforcement) and special interest groups. Information security should be independently reviewed.

6.2 Mobile Devices and Teleworking

Mobile devices are being used extensively within organisations and it is vital that the security of business information is protected. This is particularly important when working outside the organisation in unprotected environments.

Mobile devices should be protected from theft and where possible should have the ability to be remotely wiped of information when needed.

Section 7:  Human Resources Security

The organisation should manage system access rights etc. for ‘new starters, promotion and leavers’, and should undertake suitable security awareness, training and educational activities.

7.1 Prior to Employment

Background verification checks should be carried out  in accordance with relevant laws, regulations and ethics and should be proportionate  to the business requirements, the classification of the information to be accessed and the perceived risks. 

Security responsibilities should be taken into account when recruiting permanent employees, contractors and temporary staff through adequate job descriptions, pre-employment screening and included in contracts (e.g. terms and conditions of employment and other signed agreements on security roles and responsibilities).

7.2  During Employment

The organisation should ensure that employees, contractors and third party users are properly briefed about information security threats and concerns and their responsibilities regarding information security should be defined. Employees and (if relevant) third party IT users should be made aware, educated and trained in security procedures. A formal disciplinary process is necessary to handle security breaches.

7.3 Termination  and Change of Employment

Security aspects of a person’s exit from the organisation are managed (e.g. the return of company assets and removal of access rights, change of access codes or passwords). Clearly some of the controls are different if the person has been dismissed and must leave the premises immediately.

Changes in roles should be managed and the termination of current responsibility or employment combined with the start of new responsibility or employment.

Section 8:  Asset Management

Assets associated with information and information processing should be identified and appropriate protection responsibilities defined.

8.1  Responsibility for Assets

The organisation should identify assets relevant in the lifecycle of information and document their importance.  The lifecycle information should include creation, processing, storage, transmission, deletion and destruction. Documentation should be maintained in dedicated or existing inventories as appropriate.

The Asset inventory should be accurate, up to date, and consistent and aligned with other inventories.
Ownership of assets and their classification should be defined

8.2 Information Classification

Information should be classified in terms of legal requirements, value, criticality and sensitivity to unauthorised disclosure or modification.

It is usual to apply the test of analysis of the effect on Confidentiality, Integrity and Availability.
Examples can be based on four levels:

  • Disclosure causes no harm   –   Public domain
  • Disclosure causes minor embarrassment or minor operational inconvenience  – Restricted
  • Disclosure has a significant short term impact on operational or tactical objectives – Confidential
  • Disclosure has a serious impact on long term strategic objectives or puts the survival of the organisation at risk – Secret

 

Section 8.3 Media

To prevent unauthorised disclosure, modification, removal or destruction of information stored on media.

Removable media should be protected and stored in accordance with the organisation’s security classifications/.

Media contents no longer required should be made unrecoverable.

If data confidentiality or integrity are important considerations then cryptography techniques should be considered.

Registration of removable media should be considered to limit the opportunity for data loss.

Removable media drives should only be enabled if there is a business case for doing so.

Media that is no longer required should be disposed of securely. Audit trails of these media should be maintained.

Section 9: Access Control

Logical access to IT systems, networks and data must be suitably controlled to prevent unauthorised use.

9.1 Business Requirement for Access Control

The organisation’s requirements to control access to information assets should be clearly documented in an access control policy, including for example job-related access profiles (role based access control). [This is an important obligation for information asset owners.]

9.2  User Access Management

Formal procedures for the allocation of access rights to users should be controlled through user registration and administration procedures (from initial user registration through to removal of access rights when no longer required), including special restrictions over the allocation of privileges and management of passwords, and regular access rights reviews.

9.3 User Responsibilities

Users should be made accountable for safeguarding their authentication information. e.g. keeping their secret authentication confidential and not divulging to any other parties, including those in authority. SSO (Single Sign On and other secret authentication information management tools reduce the amount of secret authentication information that users are required to protect and this can increase the effectiveness of this control. However, these tools can also increase the impact of disclosure of secret authentication information.

9.4  System and Application Access Control

Access to information and application system functions should be restricted in accordance with the access control policy.

The following may be considered:

  • Providing menus to control access to application systems function;
  • Controlling which data can be accessed by a particular user;
  • Controlling read, write, delete and execute functions;
  • Controlling the access rights of other applications;
  • Limiting information contained in outputs;
  • Providing physical or logical access controls for the isolation of sensitive applications or applications data or systems.

Password management systems should be employed to ensure that secure log-on procedures are followed, including the use of strong passwords and regular changing of these passwords.

Section 10:  Cryptography

A cryptography policy should be developed and implemented.  This should include:

  • The required level of protection required;
  • The type, strength, and quality of the encryption algorithm to be used;
  • Key management;
  • Integrity/authenticity of using digital signature or message authentication codes;

Section 11:  Physical and Environmental Security

Critical or sensitive information processing facilities should be physically protected against malicious or accidental damage or loss, overheating, loss of mains power etc.  It should also be sited to prevent unauthorised viewing of confidential matter.

There is a need for concentric layers of physical controls including barriers, walls, card controlled entry gates or manned reception desks (rather like  an onion) to protect sensitive IT facilities from unauthorised access.

A secure area may be a lockable office, a computer room or several rooms surrounded by a continuous internal physical security barrier.

Critical IT equipment, cabling and other assets should be protected against physical damage, fire, flood, theft, and interception etc., both on and off-site.

Power supplies and cabling should be secured. IT equipment should be maintained properly and disposed of securely.

Access to and within application systems should be controlled in accordance with a defined access control policy. Particularly sensitive applications may require dedicated (isolated) platforms, and/or additional controls if run on shared platforms.

The application of physical controls should be adapted to the technical and economic circumstances of the organisation.

11.2 Equipment

To prevent loss, damage, theft or compromise of assets and interruption to the organisation’s operations.

This includes the siting of equipment to reduce the risks from environmental threats and hazards, and opportunities for unauthorised access.

Supporting utilities should be inspected regularly to detect damage and malfunction.

Cabling should be protected and checked for unauthorised interception.

Clear desk and clear screen policies should be in use.

Section  12:  Operations Security

This is a big clause and it covers all aspects of operations security.

To ensure correct and secure operations of information processing facilities.

Documented operating procedures should be available to all users who need them.

Change control procedures should be used to record and authorise changes to the organisation, business processes, information processing facilities and systems that can affect information security.

Capacity management should be monitored, tuned and projections made of future capacity requirements to ensure the required system performance,

12.2 Protection from malware

To ensure that information and information processing facilities are protected from Viruses and other malware.

12.3  Backup

Systems  should be backed up to protect against data loss.

12.4    Logging and monitoring

To record events and generate evidence.

12.5    Control of operational software

To ensure the integrity of operational systems.

12.6  Technical vulnerability management

To prevent exploitation of technical vulnerabilities.

12.7   Information systems audit considerations

To minimise the impact of audit activities on operational systems.

Section 13: Communications security

This is a big clause and covers all aspects of communications security

To ensure the protection of information in networks and its supporting information processing facilities.

Section 14: Information Systems acquisitions, development and Maintenance

To ensure that information security must take into account the Systems Development Lifecycle (SDLC) processes for specifying, building/acquiring, testing, implementing and maintaining IT systems.

14.1 Information Security Requirements analysis and specifications

Automated and manual security control requirements should be analysed and fully identified during the requirements stage of the systems development or acquisition process, and incorporated into business cases. Purchased software should be formally tested for security, and any issues risk-assessed.

14.2 Security in development and support processes

To ensure that information security is designed within the development lifecycle of information systems.

14.3 Test data

To ensure the protection of data used for testing.

Section  15:  Supplier relationships

This new section deals with the protection provided in supplier agreements.

Section 16: Information Security Incident Management

Information security events, incidents and weaknesses (including near-misses) should be promptly reported and properly managed.

16.1 Reporting Information Security Events and Weaknesses

A formal incident/weakness reporting procedure is required, plus the associated response and escalation procedures. There should be a central point of contact, and all employees, contractors etc. should be informed of their incident reporting responsibilities.  Feedback to the person reporting an incident should take place.

16.2 Management of Information Security Incidents and Improvements

Responsibilities and procedures are required to manage incidents and weaknesses effectively, to implement continuous improvement (learning the lessons), and to collect evidence in accordance with legal requirements.

Section 17: Information Security Aspects of Business Continuity Management                                            

This section describes the objective to counteract interruptions to business activities and to protect critical business processes from the effects of major failures of information systems or disasters and to ensure their timely resumption. A business continuity management process should be implemented to minimise the impact on the organisation and recover from the loss of information assets.

The relationship between IT disaster recovery planning, business continuity management and contingency planning, ranging from analysis and documentation through to regular exercising/testing of the plans. These controls are designed to minimize the impact of security incidents that happen despite the preventive controls noted elsewhere in the standard.

Section 18: Compliance

18.1 Compliance with Legal and Contractual Requirements

The organisation must comply with applicable legislation such as copyright, data protection, protection of financial data and other vital records, cryptography restrictions, rules of evidence etc.

18.2  Information Systems Reviews

System audits should be carefully planned to minimise disruption to operational systems. Powerful audit tools/facilities must also be protected against unauthorised use.

The official blog for independent Management Training
Consultancy, Quality Matters Limited.

If you thought the Wannacry Ransomeware worm which brought a vast number of computer systems to their knees was a major disaster, then watch out for this next one.  EternalRocks uses 7 leaked NSA hacking tools.  These were developed by the American Security Agency to hack into enemy systems, however the leaked versions are now being used to extort money worldwide.

This new one doesn’t alert the user that the system is infected until 24 hours later, hoping that a backup of the infected system will have been made and make restore more difficult.
The worm does not have a ‘kill switch’ which halted the spread of Wannacry.  It is looking for systems to infect and then demand a fee for the decrypt key. The vulnerability uses unpatched SMB ports.

We understand that systems which have the latest operating systems and are patched should be ok.    Certificated users with ISO 27001 will be aware of the requirements for this.

It is vital that organisations have good backups of data and that these backups are fully verified so that they can be installed in case of a problem. It is too late when a restore fails through an unverified backup or the backup is corrupted.

Cyber Crime is fast becoming the number one risk.

The official blog for independent Management Training
Consultancy, Quality Matters Limited.

IS0 27001 is a Model for information security management systems. It is an information security system registration scheme where a company’s information security procedures and processes are assessed to an information security management Standard.  This Standard has been agreed in this country, the European Union and Internationally

ISO 27001 is the working standard and it contains 7 main sections

  1. Scope
  2. Normative References
  3. Terms and definitions
  4. Context of the Organisation
  5. Leadership
  6. Planning
  7. Support
  8. Operation
  9. Performance Evaluation
  10. Improvement

Put very simply, ISO 27001 is a declaration of an organisations ability to demonstrate its capability to consistently protect information security and to satisfy its customers’ information security needs.

Risk Assessments

Risk assessments must be carried out on important parts of the organisation; risks evaluated and a risk treatment plan established to mitigate the risk.  Where medium risks cannot be reduced then it is permitted to accept the risk based on certain criteria.

Risk assessments have been carried out on each asset.

The methodology used identifies the Asset Value:

  1. Low value to the business
  2. Moderate importance to the business
  3. Highly important to the business

Following the risk assessment the results are reviewed at an ISMS Forum meeting.

Scores are either confirmed or adjusted as necessary.

Items which are seen as high risk are addressed with the highest priority.

Risk assessments are revisited and actions taken as necessary.  Issues which are identified in the interim as high risk will be addressed immediately if, in the opinion of management, delay would be detrimental to the company.

 Statement of Applicability

The Statement of Applicability (S.O.A) is a document that is available to the public and is attached to the Certificate of compliance issue by the Certification Body. It details all the elements of the standard that are applicable, and those which are excluded and a justification for exclusions.
Annex A of ISO 27001 contains all the controls applicable to an application.

Clearly not all organisations will apply all elements of the Standard and this document details which are used.

The S.O.A is version controlled and any change must be notified to the Certification Body.

The official blog for independent Management Training
Consultancy, Quality Matters Limited.

Holders of the ISO 27001:2005 Standard will be aware that the “Clock is ticking” and they must upgrade to the new 2013 Standard by September 2015 or risk being de-registered.  However most organisations are being cautious not to rush the transition and perhaps get a system that is too complicated or difficult to maintain.

This is the third part of our series detailing the various steps needed to achieve a successful transition to the revised Standard.

The RISK ASSESSMENT PROCESS identifies the risk to the organisation and prioritises the risk as a High. Medium or Low risk; once these have been determined then it is necessary to transfer the high and medium risks into a risk treatment plan, but more of that later.
The first step is to identify which assets are to be included in the risk assessment process; these are normally entered into an asset register.

Some examples of these assets will be:

  • Accounts
  • computer back-up systems
  • internal computer operating and package systems
  • desktops, laptops and servers,  
  • active directory, 
  • data links, 
  • VPN
  • Other remote connections, telephony and voice recording, human resources, buildings, utilities and emergency power systems, 
  • Secure storage of documents and records.  

This list is not exhaustive and will need to be tailored to individual organisations.

The next step is to decide on the value to the organisation; this is not necessarily the monetary value to the organisation but the value in terms of information security.  You could use any scale but for ease we tend to use low medium and high value (1, 2 or 3)

Now score each asset against the three main elements of 27001, C.I A. Confidentiality, Integrity and Availability, again using the low , medium or high method.  The scores are entered into a matrix.

Every medium or high risk is transferred to the risk treatment plan mentioned before.  The idea is to mitigate the risk.  Inevitably there will be some medium risks that will have to be accepted as acceptable, it is most unlikely that any risk in the high level would be acceptable.  The medium risks that are accepted by the management of the organisation should fall into four categories:

  • Applying appropriate controls to reduce the risk
  • Knowingly and objectively accepting risks, providing they clearly satisfy the organisation policy and criteria for risk acceptance
  • Avoiding risks by not allowing actions that would cause the risk to occur
  • Transferring the associated risks to other parties. e.g. insurers or suppliers

There are other methods that can be used for risk assessment and these are equally valid.  We feel that it is important to have a risk assessment process that is effective but easy to administer and our method meets these criteria.

Stage four of this series will look at the documentation needed for this revised Standard.

The official blog for independent Management Training
Consultancy, Quality Matters Limited.

Once again there have been cases where sensitive data has been left on trains or in restaurants and most of these are either laptops, or memory devices.  The sheer volume of data loss is reaching epidemic proportions.
  
ISO27001 is a good system to have in place but it must be enforced vigorously, otherwise it is just too easy to allow data to be lost or removed.

The prime method for theft of data remains the USB stick and this seems to be the method of choice for those wishing to steal data from systems.

There are a couple of things you can do to protect your data:

  • Set up computers and laptops to exclude USB devices and CD/DVD writers.  It may seem harsh for laptop users not to be able to use the USB port, apart from a mouse but if the data you hold is sensitive then this level of protection is justifiable. 
  • Using group policy to prevent the export of data by email or other attachment. 
  • Enforce the encryption policy to make sure that any data stored on a laptop is secure; password protection alone is not enough.
  • You could also set up your laptop systems to be ‘thin client’, that is to have all data stored on a server and using the laptop to connect to the server.  No data can be stored on the laptop,  so the laptop cannot be compromised.
  • And finally ensure that paper documents are protectively marked if they are sensitive and enforce security protocols for restricted, confidential and secret documents.

Let us all make sure that 2010 is not going to be a year when we lose data.

The official blog for independent Management Training
Consultancy, Quality Matters Limited.