ISO 27001-2005 ISMS Implementation Checklist

ISO 27001:2005 ISMS Implementation Checklist

Interviewee: Interviewer: Date: Instructions on Use: 1. The purposes for this implementation / interview checklist are to: a) Gauge the level of compliance to ISO 27001:2005 Information Security Mgmt System Requirements by your group / dept / division b) Facilitate the provision of information necessary for ISO 27001:2005 implementation c) Serve as a training materials for understanding the ISO 27001:2005 requirements Please spend about 2-3 hours going through the checklists, answering the questions to the best of your knowledge. The Interviewer will go through the questions with you to help you to answer some of the questions during the interview session. Please also provide a copy (where available) of the following: Documentation, records, procedures, flow-charts relating to the questions posed in this interview checklist. The key areas covered by the ISO 27001:2005 ISMS Requirements include: a) 4 ISMS Requirements : 4.1 General Requirements for ISMS, 4.2 Establishing & Managing the ISMS, 4.2.1 Establishing the ISMS, 4.2.2 Implement and Operate The ISMS, 4.2.3 Monitor & Review The ISMS, 4.2.4 Maintain & Improve The ISMS, 4.3 Documentation Requirements, 4.3.1 General Documentation Requirements, 4.3.2 Control of Documents, 4.3.3 Control of Records b) 5 Mgmt Responsibilities: 5.1 Mgmt Commitment, 5.2 Resource Mgmt c) 6 Internal ISMS Audits d) 7 Mgmt Review of ISMS: 7.1 General Mgmt Review Requirements, 7.2 Review Input, 7.3 Review Output e) 8 ISMS Improvement: 8.1 Continual Improvement, 8.2 Corrective Action, 8.3 Preventive Action f) Annex A: Control Objectives and Controls : 1. A5 Security Policy: A5.1 Information Security Policy 2. A6 Organisation of Information Security: A6.1 Internal Organisation, A6.2 External Parties 3. A7 Asset Mgmt : A7.1 Responsibility For Assets, A7.2 Information Classification ____________________ ____________________ ____________________ Designation: ____________________

2.

3. a) 4.

105719266.doc (Oct 2007)

Page 1 of 32

ISO 27001-2005 ISMS Implementation Checklist 4. A8 Human Resource Security: A8.1 Prior To Employment, A8.2 During Employment, A8.3 Termination or Change of Employment 5. A9 Physical & Environmental Security: A9.1 Secure Areas, A9.2 Equipment Security 6. A10 Communications & Operations Mgmt : A10.1 Operational Procedures and Responsibilities, A10.2 3rd Party Service Delivery Mgmt, 10.3 System Planning and Acceptance, A10.4 Protection Against Malicious & Mobile Code, A10.5 Information Back-up, A10.6 Network Security Mgmt, A10.7 Media Mgmt, A10.8 Exchange of Information, A10.9 Electronic Commerce Service, A10.10 Monitoring 7. A11 Access Control : A11.1 Biz Requirement for Access Control, A11.2 User Access Mgmt, A11.3 User Responsibilities, A11.4 Network Access Control, A11.5 Operating System Access Control, A11.6 Application and Information Access Control, A11.7 Mobile Computing and Tele-working 8. A12 Information System Acquisition, Development & Maintenance: A12.1 Security Requirements of Information Systems, A12.2 Correct Processing In Applications, A12.3 Cryptographic Controls, A12.4 Security of System Files, A12.5 Security in Development and Support Processes, A12.6 Technical Vulnerability Mgmt 9. A13 Information Security Incident Mgmt : A13.1 Reporting Information Security Events and Weaknesses, A13.2 Mgmt of Information Security Incidents and Improvements 10. A14 Business Continuity Mgmt : A14.1 Information Security Aspects of Business Continuity Planning 11. A15 Compliance : A15.1 Compliance with Legal Requirements, A15.2 Compliance With Security Policies & Standards, and Technical Compliance, A15.3 Information Systems Audit Considerations ISO 27001-2005 ISMS Requirements 4 Information Security Mgmt System 4.1 General Requirements For ISMS Is the documented Information Security Mgmt System (ISMS) established, implemented, operated, monitored, reviewed, maintained and improved? Does it address the 12. Overall business activities? 105719266.doc (Oct 2007) Page 2 of 32 Yes No Partial N.A.

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements 13. The risks that it faces? Remarks (if any): Yes No Partial N.A.

4.2 Establishing and Managing the ISMS 4.2.1 Establish the ISMS a) Are the scope and boundaries of the ISMS defined in term of the characteristic of the business, the organisation, its location, assets and technology, including details of and justifications for any exclusion from the scope? b) Is the ISMS policy defined and approved by Mgmt? 14. Does the ISMS policy provide a framework for setting objectives and establishes an overall sense of direction and principles for action with regard to information security? Does the ISMS policy take into account business, legal, regulatory requirements and contractual security obligations? Does the ISMS policy establishes the criteria against which risk will be evaluated? c) Is the risk assessment approach defined and suited to the ISMS, identified business information security, legal and regulatory requirements? Does the risk assessment approach helps to develop the criteria for accepting risks and identify the acceptable level risk? d) Are the following identified during the risk assessment? Assets within the scope of the ISMS and the owners of these assets The threats to these assets The vulnerabilities that might by exploited by the threats The impact in terms of loss of availability, integrity and confidentiality for these assets e) Are the risks analysed and evaluated in terms of: The business impacts upon the organisation that might results from the security failures The realistic likelihood of security failures occurring in the light of prevailing threats and vulnerabilities The level of estimated risk Whether the risks are acceptable or requirement treatment using the criteria for accepting risks identified in 4.2.1c f) Are the options for the treatment of the risks identified and evaluated? Risks can be mitigated, accepted, avoided or transferred 105719266.doc (Oct 2007) Page 3 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements to other parties g) Are the control objectives and controls for the treatment of risks selected? h) Is mgmt approval obtained for the proposed residual risks? i) Has mgmt authorisation been obtained to implement and operate the ISMS? j) Is a Statement of Applicability prepared and does it include the following? Control objectives and controls selected in 4.2.1.g and the reasons for their selection Control objectives and controls currently implemented Exclusion of any control objectives and controls in Annex A of the ISO 27001:2005 Std and the justification for their exclusion Remarks (if any): 4.2.2 Implement and Operate the ISMS a) Is a risk treatment plan formulated to identify the appropriate mgmt action, resources, responsibilities and priorities for managing information security risks? b) Is the risk treatment plan implemented in order to achieve the identified control objectives, which includes consideration of funding and allocation of roles and responsibilities c) Are the selected security controls in 4.2.1.g implemented to meet the control objectives? d) Is the measuring of the effectiveness of the selected security controls or group of controls defined? 30. Does this measurement produce comparable and reproducible results? Is the specification on how this is done recorded? e) Are the ISMS training and awareness programmes implemented? f) Is the operation of the ISMS managed? g) Are the resources for the ISMS managed? h) Are the procedures and other controls capable of enabling prompt detection of security events and response to security incidents implemented? Remarks (if any): Yes No Partial N.A.

105719266.doc (Oct 2007)

Page 4 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements 4.2.3 Monitor & Review the ISMS a) Are monitoring and reviewing procedures and other controls executed? 31. Are errors in the results of processing promptly detected? 32. Are attempted and successful security breaches and incidents promptly identified? Is mgmt able to determine whether security activities delegated to people or implemented by information security are performing as expected? Are security events and prevention of security incidents detected by the use of indicators Are the actions taken to resolve a breach of security determined as effective? b) Are regular reviews of the effectiveness of the ISMS (including meeting of ISMS policy and objectives and review of security controls) undertaken? Are the results of security audits, incidents, and results from effectiveness measurements, suggestions and feedback from interested parties taken into account? c) Is the effectiveness of controls to verify that the security requirements have been met measured? d) Are risk assessments at planned intervals reviewed? Are the residual risks and identified acceptable levels of risks review? Are the following taken into account? 1) The organisation, 2) technology, 3) business objectives and processes, 4) Identified threats, 5) Effectiveness of the implemented controls, 6) External events such as changes to the legal or regulatory environmental, etc. e) Are internal ISMS audits at planned intervals conducted? f) Is a mgmt review of the ISMS on a regular basis undertaken to ensure that the scope remains adequate and improvements in the ISMS process are identified? g) Are security plans updated to take into account eh findings of monitoring and reviewing activities h) Are actions and events that could have an impact on the effectiveness or performance of the ISMS recorded? Remarks (if any): Yes No Partial N.A.

4.2.4 Maintain and Improve the ISMS a) Are improvements to the ISMS implemented and 105719266.doc (Oct 2007) Page 5 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements identified? b) Are appropriate corrective and preventive actions taken? Are the lessons learnt from the security experience of other organisations and those of the organisation itself applied? c) Are the actions and improvements communicated to all interested parties with a level of details appropriate to the circumstances? d) Did the objectives? Remarks (if any): improvements achieve their intended Yes No Partial N.A.

4.3 Documentation Requirements 4.3.1 General Documentation Requirements Does the documentation include records of mgmt decisions? Does documentation ensure that actions are traceable to mgmt decisions and policies? Does the ISMS Documentation include: a) Documented statements of the ISMS policy (4.2.1.b) and objectives? b) The scope of the ISMS (4.2.1.a) c) Procedures and controls in support of the ISMS d) A description of the risk assessment methodology (4.2.1.c) e) The risk assessment report ( 4.2.1c to g) f) The risk treatment plan (4.2.2b) g) Documented procedures needed by the organisation to ensure the effective planning, operations and control of its information security processes and describe how to measure the effectiveness of controls (4.2.3c) h) Records required by this std (4.3.3) i) The statement of applicability (4.2.1j) Remarks (if any):

4.3.2 Control of Documents Are documents required by the ISMS protected and controlled? Is a documented procedure established to 105719266.doc (Oct 2007) Page 6 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements define mgmt actions for the following? a) Approve documents for adequacy prior to issue Yes No Partial N.A.

b) Review and update documents as necessary and re-approve documents c) Ensure that changes and the current revision status of documents are identified

d) Ensure that relevant versions of applicable documents are available at points of use e) f) Ensure that documents remain legible and readily identifiable Ensure that documents are available to those who need them, and are transferred, stored and ultimately disposed of in accordance with the procedures applicable to their classification

g) Ensure that documents of external origin are identified h) Ensure that the distribution of documents is controlled Prevent the unintended use of obsolete documents and apply suitable identification to them if they are retained for any purpose. Remarks (if any): i)

4.3.3 Control of Records Are records established and maintained to provide evidence of conformity to the requirements and the effective operations of the ISMS? 38. Are these records protected and controlled? 39. Are relevant legal or regulatory requirements and contractual obligations taken into account for control of records? 40. Are the records legible, readily identifiable and retrievable? 41. Are controls needed for the identification, storage, protection, retrieval, retention time and disposition of records documented and implemented? Remarks (if any): 105719266.doc (Oct 2007) Page 7 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements Yes No Partial N.A.

Mgmt Responsibility

5.1 Mgmt Commitment Are there evidence of mgmt commitment to the establishment, implementation, operation, monitoring, review, maintenance and improvement of the ISMS? a) Is mgmt involved in establishing the ISMS policy?

b) Does mgmt ensure that the ISMS objective and plans are established? c) Does mgmt establish roles and responsibilities for information security?

d) Does mgmt communicate to the organisation on the importance of meeting the information security objectives, conforming to the information security policy and the need for continual improvement? e) Does mgmt provide sufficient resources to establish, implement, operate, monitor, review, maintain and improve the ISMS? Does mgmt decide on the criteria for accepting risks and the acceptable levels of risks?

f)

g) Does mgmt ensure that internal ISMSS audits are conducted? h) Does mgmt conduct mgmt reviews of the ISMS? Remarks (if any):

5.2 Resource Mgmt 5.2.1 Provision of Resource Does the organisation determine and provide resources need to: a) Establish, implement, operate, monitor, review, maintain and improve the ISMS? security business

b) Ensure that the information procedures support the requirements? c)

Identify and address legal and regulatory requirements and contractual security obligations? Page 8 of 32

105719266.doc (Oct 2007)

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements d) Maintain adequate security by correct application of all implemented controls e) Carry out reviews when necessary, and to react appropriately to the results of these reviews? Yes No Partial N.A.

Where required, improve the effectiveness of the ISMS? Remarks (if any):

f)

5.2.2 Competence, Training & Awareness Does the organisation ensure that all personnel are assigned responsibilities defined in the ISMS are competent to perform the required tasks by: a) Determining the necessary competencies for personnel performing work effecting the ISMS?

b) Providing training or taking other actions to satisfy these needs? c) Evaluating the effectiveness of the actions taken?

d) Maintaining records of education, training skill, experience and qualifications? Does the organisation ensure that all relevant personnel are aware of the relevance and importance of the information security activities and how they contribute to the achievement of the ISMS objectives? Remarks (if any):

Internal ISMS Audits

Does the organisation conduct internal ISMS audits at planned intervals to determine whether the control objectives, controls, processes and procedures of the ISMS: a) Conform to the requirements of this standard and relevant legislation or regulations?

b) Conform to the identified information security requirements? c) Are effectively implemented and maintained? d) Performed as expected? Is an audit programmed planned, taking into consideration 105719266.doc (Oct 2007) Page 9 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements the status and importance of the processes and areas to be audited, as well as the results of the previous audits? Are the audit criteria, scope, frequency and methods defined? Are auditors selected and audits conducted in an objective and impartial manner? Is there a check to ensure that auditors do not audit their own work? Are the responsibilities and requirements for the planning, conduct of audits, reporting results and maintaining records defined in a documented procedure? Do the mgmt responsible for the area being audited ensure audit follow-up actions are taken in a timely manner? Are audit follow-up actions verified and reported? Remarks (if any): Yes No Partial N.A.

7 Mgmt Review of The ISMS 7.1 General Mgmt Review Requirements Does mgmt review the organisations ISMS at planned intervals (at least once a year) to ensure its continuing suitability, adequacy and effectiveness? Does this review include assessing opportunities for improvement, need for changes to the ISMS, review of information security policy & objectives? Are the results of the reviews clearly documented and records maintained? Remarks (if any):

7.2 Review Input Are the following included in the mgmt review? a) c) Results of the ISMS audits and reviews Techniques, products or procedures that can be used to improve the ISMS performance and effectiveness Vulnerabilities or threats not adequately addressed in the previous risk assessment Page 10 of 32 b) Feedback from interested parties

d) Status of preventive and corrective actions e)

105719266.doc (Oct 2007)

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements f) Results from effectiveness measurements g) Follow-up actions from previous mgmt reviews h) Any changes that could affect the ISMS i) Recommendation for improvement Remarks (if any): Yes No Partial N.A.

7.3 Review Output Does the output from the mgmt review include decisions and actions relating to? a) Improving the effectiveness of the ISMS b) Update of the risk assessment and risk treatment plan c) Modification of procedures and controls that effect information security, as necessary, to respond internal or external events that may impact the ISMS Business

d) Changes to: 42. 43. 44. 45. 46. 47. requirements Security requirements Business processes effecting the existing business requirements Regulatory or legal requirements Contractual obligations Level of risk and / or criteria for accepting risks e) f) Resource needs

Improvements to how the effectiveness of controls is measured Remarks (if any):

8 ISMS Improvement 8.1 Continual Improvement Does the organisation continually improve the Page 11 of 32

105719266.doc (Oct 2007)

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements effectiveness of the ISMS through the use of the 48. Information security policy & objectives 49. Audit results & analysis of monitored events 50. Corrective & preventive actions 51. Mgmt review? Remarks (if any): Yes No Partial N.A.

8.2 Corrective Action Does the organisation take action to eliminate the cause of non-conformities with the ISMS requirements in order to prevent recurrence? Does the documented procedures for corrective actions define requirements for: a) c) Identifying non-conformities Evaluating the need for actions to ensure that non-conformities do not recur b) Determining the causes of non-conformities

d) Determining and implementing the corrective action needed e) Recording results of action taken and f) Reviewing of corrective action taken Remarks (if any):

8.3 Preventive Action Does the organisation take action to eliminate the cause of potential non-conformities with the ISMS requirements in order to prevent their occurrence? Are preventive actions taken appropriate to the impact of the potential problems? Does the documented procedures for preventive actions define requirements for: a) Identifying potential non-conformities Page 12 of 32

105719266.doc (Oct 2007)

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements b) Evaluating the need for actions to prevent occurrence of the potential non-conformities c) Determining and implementing the preventive action needed Reviewing of preventive action taken Yes No Partial N.A.

d) Recording results of action taken and e) Is the priority of the preventive action determined based on the results of the risk assessment? Remarks (if any):

Annex A Control Objectives and Controls

A5 Security Policy A5.1 Information Security Policy Objective: Is there an information security policy to provide mgmt direction and support for information security in accordance with business requirements, relevant laws and regulations? A5.1.1: Information Security Policy Document Is an information security policy document approved by mgmt, published and communicated to all employees and relevant external parties? A5.1.2: Review of the Information Security Policy: Is the information security policy reviewed at planned intervals or if significant changes occur to ensure its continuing suitability, adequacy and effectiveness? Remarks (if any):

A6 Organisation Of Information Security A6.1 Internal Organisation Objective: Is information security managed within the organisation? A6.1.1 Mgmt Commitment To Information Security: Is mgmt actively supporting security within the organisation through clear direction, demonstrated commitment, explicit assignment and acknowledgement of information security responsibilities? A6.1.2 Information Security Co-ordination: Is information 105719266.doc (Oct 2007) Page 13 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements security activities co-ordinated by representatives from different parts of the organisation with relevant roles and job functions? A6.1.3 Allocation of Information Responsibilities: Are all information responsibilities clearly defined? Security security Yes No Partial N.A.

A6.1.4 Authorisation Process: Is mgmt authorisation process for new information processing facilities defined and implemented? A6.1.5 Confidentiality Agreements: Are requirements for confidentiality or non-disclosure agreements reflecting the organisations needs for the protection of information defined and regularly reviewed? A6.1.6 Contact With Authorities: Are appropriate contacts with relevant authorities maintained? A6.1.7 Contact With Special Interest Groups: Are appropriate contacts with special interest groups or other specialist security forum and professional associations maintained? A6.1.8 Independent Review of Information Security: Is the organisations approach to managing information security and its implementation (e.g. control objectives, controls and policies, processes and procedures) reviewed independently at planned intervals or when significant changes to the security implementation occur? Remarks (if any):

A6.2

External Parties

Objective: Is the security of organisations information and information processing facilities maintained when these are accessed, processed, communicated to or managed by external parties? A6.2.1 Identification of Risks Related to External Parties: Are the risks to the organisations information and information processing facilities identified and appropriate controls implemented before granting access to external parties? A6.2.2 Addressing Security When Dealing With Customers: Have all identified security requirements been addressed before giving customer access to the 105719266.doc (Oct 2007) Page 14 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements organisations information or assets? A6.2.3 Addressing Security in 3rd Party Agreements: Do agreements with 3rd parties involving accessing, processing, communicating or managing the organisations information or information processing facilities cover all relevant security requirements? Remarks (if any): Yes No Partial N.A.

A7 Asset Mgmt A7.1 Responsibility For Assets Objective: Is the appropriate protection of organisation assets achieved and maintained? A7.1.1 Inventory of Assets: Is an inventory of all important assets drawn up and maintained? Are all sets cleared identified? A7.1.2 Ownership of Assets: Are all information and assets associated with information facilities owned by a designated part of the organisation? A7.1.3 Acceptable Use of Assets: Are rules for the acceptable use of information and assets associated with information processing facilities identified, documented and implemented? Remarks (if any):

A7.2 Information Classification Objective: Does each information asset receive an appropriate level of protection? A7.2.1 Classification Guidelines: Is information classified in terms of its value, legal requirements, sensitivity and criticality to the organisation? A7.2.2. Information Labelling and Handling: Is an appropriate set of procedures for information labelling and handling developed and maintained in accordance with the classification scheme adopted by the organisation? Remarks (if any):

105719266.doc (Oct 2007)

Page 15 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A8 Human Resource Security A8.1 Prior To Employment Objective: Do employees, contractors and 3rd party users understand their responsibilities and roles to reduce the risk of theft, frauds or misuse of facilities? A8.1.1 Roles & Responsibilities: Are security roles and responsibilities of employees, contractors and 3rd party users defined and documented in accordance with the organisations information security policy? A8.1.2 Personnel Screening: Are background verification checks on all candidates for employment, contractors, and 3rd party users carried out in accordance with relevant laws, regulations and ethics, and proportional to the business requirements, the classification of the information to be accessed, and the perceived risks? A8.1.3 Terms & Conditions of Employment: Are employees, contractors, and 3rd party users required to agree and sign the terms and conditions of their employment contract which states their and the organisation's responsibilities for information security? Remarks (if any): Yes No Partial N.A.

A8.2 During Employment Objective: Are all employees, contractors and 3rd party users aware of information security threats & concerns, their responsibilities and liabilities? Are all employees, contractors and 3rd party users equipped to support the organisational security policy in the course of their normal work, and to reduce risk of human error? A8.2.1 Mgmt Responsibilities: Does mgmt required employees, contractors and 3rd party users to apply security in accordance with established policies and procedures of the organisation? A8.2.2 Information Security Training, Education & Awareness: Do all employees of the organisation and where relevant, contractors and 3rd party users receive appropriate awareness training and regular updates in organisational policies and procedures, as relevant for their job function? A8.2.3 Disciplinary Process: Is there a formal disciplinary 105719266.doc (Oct 2007) Page 16 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements process for employee who has committed a security breach? Remarks (if any): Yes No Partial N.A.

A8.3 Termination or Change of Employment Objective: Do employees, contractors and 3rd party users exit an organisation or change employment in an orderly manner? A8.3.1 Termination Responsibilities: Are responsibilities for performing employment termination or change of employment clearly defined and assigned? A8.3.2 Return of Assets: Are all employees, contractors and 3rd party users required to return all of the organisation's asset in their possession upon termination of their employment, contract or agreement? A8.3.3 Removal of Access Rights: Are the access rights of all employees, contractors and 3rd party users to information and information processing facilities removed upon termination of their employment, contract or agreement, or adjusted upon change? Is damage from incidents and malfunctions minimized through a system of monitoring and learning from such incidents? Remarks (if any):

A9 Physical and Environmental Security A9.1 Secure Areas Objective: Are unauthorised physical access, damage and interference to organisation's premises and information prevented? A9.1.1 Physical Security Perimeter: Are security perimeters (e.g. walls, card-controlled entry gates or manned reception desk) used to protect areas which contain information and information processing facilities? A9.1.2 Physical Entry Controls: Are secure areas protected by appropriate entry controls to ensure that only authorised personnel are allowed access? A9.1.3. Secured Offices, Rooms and Facilities: Are physical security for offices, rooms and facilities designed 105719266.doc (Oct 2007) Page 17 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements and applied? A9.1.4 Protecting Against External and Environmental Threats: Is physical protection against damage from fire, flood, earth-quake, explosion, civil unrest and other forms of natural or man-made disaster designed & applied? A9.1.5 Working In Secure Areas: Are physical protection and guidelines for working in secure areas designed and applied? A9.1.6 Public Access, Delivery & Loading Areas: Are access points such as delivery and loading areas (& other points) where unauthorised persons may enter the premises controlled, and if possible, isolated from information processing facilities to avoid unauthorised access? Remarks (if any): A9.2 Equipment Security Objective: Is the loss, damage, theft or compromise of assets and interruptions to the organisation's activities prevented? A9.2.1 Equipment Siting and Protection: Are equipment sited or protected to reduce risks from environmental threats and hazard, and opportunities for unauthorised access? A9.2.2 Supporting Utilities: Are equipment protected from power failures and other disruptions caused by failures in supporting utilities? A9.2.3 Cabling Security: Are power and telecommunications cabling carrying data or supporting information services protected from interception or damage? A9.2.4 Equipment Maintenance: Are equipment correctly maintained to ensure its continued availability and integrity? A9.2.5 Security of Equipment Off-Premises: Is security applied to off-site equipment taking into account the different risks of working outside the organisation's premises? A9.2.6 Secure Disposal or Re-use of Equipment: Are all items of equipment containing storage media checked to ensure that any sensitive data and licensed s/w as been removed or securely over-written prior to disposal or reuse? A9.2.7 Removal of Property: Is there a mechanism to ensure that equipment, information or s/w are not taken 105719266.doc (Oct 2007) Page 18 of 32 Yes No Partial N.A.

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements off-site without prior authorisation? Remarks (if any): A10 Communications and Operations Mgmt A10.1 Operational Procedures and Responsibilities Objective: Are correct and secure operations information processing facilities ensured? of Yes No Partial N.A.

A10.1.1 Documented Operating Procedures: Are the operating procedures documented, maintained and made available to all users who need them? A10.1.2 Change Mgmt: Are changes to information processing facilities and systems controlled? A10.1.3 Segregation of Duties: Are duties and areas of responsibilities segregated in order to reduce opportunities for un-authorised modification or misuse of organisation assets? A10.1.4 Separation of Development, Test and Operational Facilities: Are development, test and operational facilities separated to reduce risks of unauthorised access or changes o the operational system? Remarks (if any): A10.2 3rd Party Service Delivery Mgmt Objective: Are the appropriate level of information security and service delivery in line with the 3 rd party service delivery agreements? A10.2.1 Service Delivery: Are the security controls, service definitions and delivery levels included in the 3rd party delivery agreement implemented, operated and maintained by the 3rd party? A10.2.2 Monitoring & Review of 3rd Party Services: Are the services, reports and records provided by the 3rd party regularly monitored and reviewed? Are audits on the services, reports and records provided carried out regularly? A10.2.3 Managing Changes to 3rd Party Services: Are changes to the provision of services, including maintaining and improving existing information security policies, procedures and controls managed, taking account of the criticality of business systems and processes involved and re-assessment of risks? Remarks (if any):

105719266.doc (Oct 2007)

Page 19 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A10.3 System Planning & Acceptance Objective: Are risks of system failures minimised? A10.3.1 Capacity Mgmt: Are the use of resources monitored, tuned and projections made of future capacity requirements to ensure required system performance? A10.3.2 System Acceptance: Are acceptance criteria for new information systems, upgrades and new versions established and suitable system tests carried out during development and prior to acceptance? Remarks (if any): Yes No Partial N.A.

A10.4 Protection Against Malicious & Mobile Code Objective: Is the integrity of s/w and information protected? A10.4.1 Control Against Malicious Code: Are detection, prevention and recovery controls implemented to protect against malicious s/w? Are appropriate user awareness procedures implemented? A10.4.2 Control Against Mobile Code: Where the use of mobile code is authorised, are unauthorised mobile code prevented from being executed? Are authorised mobile codes operating according to a clearly defined security policy? Remarks (if any):

A10.5 Information Back-up Objective: Are the integrity and availability and information processing and communication services maintained? A10.5.1 Information Backup: Are back-up copies of information and s/w taken regularly in accordance with the agreed backup policy? Remarks (if any):

A10.6 Network Security Mgmt Objective: Are the protection of information in networks 105719266.doc (Oct 2007) Page 20 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements and the protection of the supporting infrastructure ensured? A10.6.1 Network Controls: Are the networks adequately managed and controlled in order to be protected from threats and to maintain security for the systems and applications using the network, including information in transit? A10.6.2 Security of Network Services: Are security features, service levels and mgmt requirements of all network services identified and included in any network services agreement, whether these services are provided inhouse or out-sourced? Remarks (if any): Yes No Partial N.A.

A10.7 Media Handling Objective: Are unauthorised disclosure, modification or destruction of assets and interruption of business activities prevented? A10.7.1 Management of Removable Computer Media: Are procedures for the management of removable computer media, such as tapes, disks, cassettes and printer reports established and implemented? A10.7.2 Disposal of Media: Are media disposed of securely and safely when no longer required, using formal procedures? A10.7.3 Information Handling Procedures: Are procedures for the handling and storage of information established to protect such information from unauthorised disclosure or misuse? A10.7.4 Security of System Documentation: Are system documentation protected against unauthorised access? Remarks (if any):

A10.8 Exchange of Information Objective: Is the security of information and s/w exchanged within an organisation and with any external entity maintained? 105719266.doc (Oct 2007) Page 21 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A10.8.1 Information Exchange Policies & Procedures: Are formal exchange policies, procedures and controls in place to protect the exchange of information through the use of all types of communication facilities? A10.8.2 Exchange Agreements: Are agreements established for the electronic or manual exchange of information and s/w between the organisation and external parties? A10.8.3 Security of Media In Transit: Is the media containing information being transported protected from unauthorised access, misuse or corruption? A10.8.4 Electronic Messaging: Is information in electronic messaging appropriately protected? A10.8.5 Business Information Systems: Are policies and procedures developed and maintained to protect information associated with the inter-connection of business information systems Remarks (if any): Yes No Partial N.A.

A10.9 Electronic Commerce Services Objective: Is the security of electronic commerce services and their secure use ensured? A10.9.1 Electronic Commerce: Is information involved in electronic commerce passing over public network protected against fraudulent activity, contract dispute and unauthorised disclosure or modification of information? A10.9.2 On-line Transactions: Is information involved in on-line transactions protected from incomplete transaction, mis-routing, unauthorised message alteration, unauthorised disclosure, unauthorised message duplication or replay? A10.9.3 Publicly Available Information: Is there a formal authorisation process before information is made publicly available and the integrity of such information protected to prevent unauthorised modification? Remarks (if any):

A10.10 Monitoring Information Processing Activities Objective: Are we able to detect unauthorised information processing activities? A10.10.1 Audit Logging: Are audit logs recording user activities, exceptions and information security events 105719266.doc (Oct 2007) Page 22 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements produced and kept for an agreed period to assist in future investigations and access control monitoring? A10.10.2 Monitoring System Use: Are procedures for monitoring use of information processing facilities established and the results of the monitoring activities reviewed regularly? A10.10.3 Protection of Log Information: Are the logging facilities and log information protected against tampering and unauthorised access? A10.10.4 Administrator and Operator Logs: Are system administrator and system operator activities logged? A10.10.5 Fault Logging: Are faults logged, analysed and appropriate action taken? A10.10.6 Clock Synchronisation: Are the clocks of all relevant processing systems within an organisation or security domain synchronised within an agreed accurate time source? Remarks (if any): Yes No Partial N.A.

A11 Access Control A11.1 Business Requirements For Access Control Objective: Is access to information controlled? A11.1.1 Access Control Policy: Is an access control policy established, documented, reviewed and implemented based on business and security requirements for access? Remarks (if any):

A11.2 User Access Management Objective: Is authorised user access to information systems ensured? Is un-authorised access to information systems prevented? A11.2.1 User Registration: Is there a formal user registration and de-registration procedure for granting and revoking access to all information systems and services? A11.2.2 Privilege Mgmt: Is the allocation and use of privileges restricted and controlled? A11.2.3 User Password Mgmt: Is the allocation of passwords controlled through a formal mgmt process? 105719266.doc (Oct 2007) Page 23 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A11.2.4 Review of User Access Rights: Do mgmt review user's access rights at regular intervals using a formal process? Remarks (if any): Yes No Partial N.A.

A11.3 User Responsibilities Objective: Are un-authorised user access, compromise or theft of information and information processing facilities prevented? A11.3.1 Password Use: Are users required to follow good security practices in the selection and use of passwords? A11.3.2 Unattended User Equipment: Are users required to ensure that unattended equipment has appropriate protection? A11.3.3 Clear Desk & Clear Screen Policy: Is a clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities adopted? Remarks (if any):

A11.4 Network Access Control Objective: Is unauthorised access to network services prevented? A11.4.1 Policy on Use of Network Services: Do users only have direct access to the services that they have been specifically authorised to use? A11.4.2. User Authentication For External Connections: Are appropriate authentication methods used to control access by remote users? A11.4.3 Equipment Identification In Network: Is automatic equipment identification considered as a means to authenticate connections from specific locations and equipment? A11.4.4 Remote Diagnostics & Configuration Port Protection: Are physical and logical access to diagnostics and configuration ports controlled? A11.4.5 Segregation in Networks: Are group of information services, users and information systems segregated on network? 105719266.doc (Oct 2007) Page 24 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A11.4.6 Network Connection Control: For shared networks, are the capability of users to connect to the network restricted in accordance with the access control policy and requirements of the business application (see A11.1) A11.4.7 Network Routing Control: Are routing controls implemented for networks to ensure that computer connections and information flows do not breach the access control policy of the business applications? Remarks (if any): Yes No Partial N.A.

A11.5 Operating System Access Control Objective: Is unauthorised access to operating systems prevented? A11.5.1 Secure Log-on Procedures: Is access to operating systems controlled by a secure log-on procedure? A11.5.2 User Identification and Authentication: Do all users have a unique identifier (user ID) for their personal use? Is a suitable authentication technique chosen to substantiate the claimed identity of a user? A11.5.3 Password Mgmt System: Is a password mgmt system in place to provide an effective, interactive facility that ensures quality password? A11.5.4 Use of System Utilities: Is the use of system utility programs that might be capable of overriding system and application controls restricted and tightly controlled? A11.5.5 Session Time-out: Are inactive sessions shut down after a defined period of inactivity? A11.5.6 Limitation of Connection Time: Are restrictions on connection times used to provide additional security for high-risk applications? Remarks (if any):

A11.6 Application & Information Access Control Objective: Is unauthorised access to information held in information systems prevented? A11.6.1 Information Access Restriction: Is access to information and application system functions by users and support staff restricted in accordance with the access 105719266.doc (Oct 2007) Page 25 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements control policy A11.6.2 Sensitive System Isolation: Do sensitive systems have a dedicated (isolated) computing environment? Remarks (if any): Yes No Partial N.A.

A11.7 Mobile Computing and Tele-working Objective: Is information security ensured when using mobile computing and tele-working facilities? A11.7.1 Mobile Computing & Communications: Is a formal policy in place and appropriate security measures adopted to protect against the risks using mobile computing and communication facilities? A11.7.2. Tele-working: Are policies, operational plans and procedures developed and implemented to authorise and control tele-working activities? Remarks (if any):

A12 Information System Acquisition Development & Maintenance A12.1 Security Requirements of Information Systems Objective: Is security an integral part of information systems? A12.1.1 Security Requirements Analysis and Specification: Do statement of business requirements for new information systems or enhancements to existing information systems specify requirements for security controls? Remarks (if any):

A12.2 Correct Processing in Applications Objective: Are errors, loss, unauthorised modification or misuse of information in applications prevented? A12.2.1 Input Data Validation: Is data input to applications validated to ensure that it is correct and appropriate? A12.2.2 Control of Internal Processing: Are validation checks incorporated into applications to detect any 105719266.doc (Oct 2007) Page 26 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements corruption of information through processing errors or deliberate acts? A12.2.3. Message Integrity: Are requirements for ensuring authenticity and protecting message integrity in applications identified, and appropriate controls identified and implemented? A12.2.4 Output Data Validation: Is data output from an application validated to ensure that the processing of stored information is correct and appropriate to the circumstances? Remarks (if any): Yes No Partial N.A.

A12.3 Cryptographic Controls Objective: Is the confidentiality, authenticity or integrity of information protected by cryptographic means? A12.3.1 Policy on the Use of Cryptographic Controls: Is a policy on the use of cryptographic controls for the protection of information developed and implemented? A12.3.2. Key Mgmt: Is key mgmt in place to support the organisation's use of cryptographic techniques? Remarks (if any):

A12.4 Security of System Files Objective: Are security of system files ensured? A12.4.1 Control of Operational S/w: Are procedures in place to control the installation of s/w on operational systems? A12.4.2 Protection of System Test Data: Are test data selected carefully, protected and controlled? A12.4.3. Access Control To Program Source Code: Is access to program source code restricted? Remarks (if any):

A12.5 Security In Development and Support Processes Objective: Is the security of application system s/w and information maintained? 105719266.doc (Oct 2007) Page 27 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements A12.5.1 Change Control Procedures: Is the implementation of changes controlled by the use of formal change control procedures? A12.5.2 Technical Review of Applications After Operating System Changes: Are business critical applications reviewed and tested to ensure that there is no adverse impact on operations or security when OS changes occur? A12.5.3 Restrictions on Changes to S/w Packages: Are modifications to s/w packages discouraged and limited to necessary changes? Are the changes strictly controlled? A12.5.4 Information Leakage: Are opportunities for information leakage prevented? A12.5.5 Outsourced S/w Development: Are outsourced s/w development supervised and monitored by the organisation? Remarks (if any): Yes No Partial N.A.

A12.6 Technical Vulnerability Mgmt Objective: Are the risks resulting from exploitation of published technical vulnerabilities reduced? A12.6.1 Control of Technical Vulnerabilities: Is timely information about technical vulnerability of information systems being used obtained? Is the organisation's exposure to such vulnerabilities evaluated and appropriate measures taken to address the associated risk? Remarks (if any):

A13 Information Security Incident Mgmt A13.1 Reporting Information Security Weaknesses

Event

&

Objective: Are information security events and weaknesses associated with information systems communicated in a manner to allow timely corrective action to be taken? A13.1.1 Reporting Information Security Events: Are information security events reported through appropriate mgmt channels as quickly as possible? A13.1.2 Reporting Security Weakness: Are all employees, contractors and 3rd party users required to note and report any observed or suspected security weaknesses in systems or services? Remarks (if any):

105719266.doc (Oct 2007)

Page 28 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements Yes No Partial N.A.

A13.2 Mgmt of Improvements

Information

Security

Incidents

&

Objective: Is there a consistent and effective approach applied to the mgmt of information security events? A13.2.1 Responsibilities & Procedures: Are mgmt responsibility and procedures established to ensure a quick, effective and orderly response to information security incidents? A13.2.2 Learning From Information Security Incidents: Are mechanism in place to enable the types, volumes and cost of incidents to be quantified and monitored? A13.2.3 Collection of Evidence: Where the information security incident involves legal action (either civil or criminal), are evidence collected, retained and presented to conform to the rules for evidence laid down in the relevant jurisdictions? Remarks (if any):

A14 Business Continuity Management A14.1 Aspects of Business Continuity Management Objective: Are interruptions to business activities counteracted and critical business processes protected from the effects of major failures or disasters? A14.1.1 Business Continuity Mgmt Process: Is there a managed process in place for developing and maintaining business continuity throughout the organisation that addresses information security requirements? A14.1.2 Business Continuity & Risk Assessment: Are events that can cause interruptions to business processes identified along with the probability and impact of such interruptions and their consequences for information security? A14.1.3. Developing & Implementing Continuity Plans: Are plans developed or maintained to restore business operations and ensure the availability of information at required level and in the required time scales following interruption in, or failure of critical business processes? A14.1.4 Business Continuity Planning Framework: Is a single framework of business continuity plans maintained to ensure that all plans are consistent in addressing various information security requirements, and to identify 105719266.doc (Oct 2007) Page 29 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements priorities for testing and maintenance? A14.1.5 Testing, Maintaining & Re-assessing Business Continuity Plans: Are business continuity plans tested & updated regularly to ensure that they are up to date and effective? Remarks (if any): Yes No Partial N.A.

A15 Compliance A15.1 Compliance with Legal Requirements Objective: Are breaches of any criminal or civil law and statutory, regulatory or contractual obligations and of any security requirements avoided? A15.1.1 Identification of Applicable Legislation: Are all relevant statutory, regulatory and contractual requirements and organisations approach to meet these requirements explicitly defined, documented and kept up to date for each information system and the organisation? A15.1.2. Intellectual Property Rights (IPR): Are appropriate procedures implemented to ensure compliance with legislative, regulatory and contractual requirements on the use of material with respect to the intellectual property rights and use of propriety s/w products? A15.1.3 Protection of Organisational Records: Are important records protected from loss, destruction and falsification, in accordance with statutory, regulatory, contractual and business requirements? A15.1.4 Data Protection & Privacy of Personal Information: Are data protection and privacy ensured as required in relevant statutory, regulatory, and if applicable contractual requirements? A15.1.5. Prevention of Misuse of Information Processing Facilities: Are users deterred from using information processing facilities for unauthorised purposes? A15.1.6 Regulations of Cryptographic Controls: Are cryptographic controls used in compliance with all relevant agreements, laws and regulations? Remarks (if any):

A15.2 Compliance With Security Policies & Standards 105719266.doc (Oct 2007) Page 30 of 32

ISO 27001-2005 ISMS Implementation Checklist ISO 27001-2005 ISMS Requirements Objective: Is the compliance of systems with organisation security policies and standards ensured? A15.2.1 Compliance with Security Policies & Standards: Do managers ensure that all security procedures within their area of responsibility are carried out correctly to achieve compliance with security policies and standards? A15.2.2 Technical Compliance Checking: Are information systems regularly checked for compliance with security implementation standards? Remarks (if any): Yes No Partial N.A.

A15.3 System Audit Consideration Objective: Is the effectiveness of the system audit process maximised? Is the interference from the system audit processed minimized? A15.3.1 Information System Audit Controls: Are audit requirements and activities involving checks on operational systems carefully planned & agreed to minimize the risk the risk of interruption to business processes? A15.3.2 Protection of Information System Audit Tools: Are access to information system audit tools protected to prevent possible misuse or compromise? Remarks (if any):

105719266.doc (Oct 2007)

Page 31 of 32