Posts Tagged ‘ISO 27001:2013 policy’

While implementing ISO 27001 Certification for compliance to ISMS (information security management system) in your organisation may seem overwhelming, you can prepare yourself for creating and managing the documentation side. Content of an Information Security Policy is certainly one of the biggest myths related to ISO 27001 – very often the purpose of this document is misunderstood, and in many cases people tend to think they need to write everything about their security in this document.

The aim of ISO 27001:2013 Policy is to define the purpose, direction, principles and basic rules for information security management. It covers guideline for controls applied as per ISO 27001:2013 Certification guidelines. The policy document templates are provided to frame the information security controls as listed below.

List of Policies required for ISO 27001:2013 Certification

  1. Acceptable Use policy-Information Services
  2. Infrastructure Policy
  3. Policy For Access Card
  4. Back up Policy
  5. Clear desk and clear Screen Policy
  6. Physical Media & Disposal Sensitive Data
  7. Electronic Devices Policy
  8. Laptop Policy
  9. Password Policy
  10. Patch Management
  11. User registration Access Management
  12. Policy for working in Secured Areas
  13. Visitor Policy
  14. Work Station Policy
  15. Cryptographic Policy
  16. LAN Policy
  17. Training Policy
  18. Mobile Computing Policy
  19. Teleworking Policy
  20. Internet
  21. Messenger And E mail
  22. Change Control
  23. Freeware and Shareware Policy

The purpose of the Information Security Policy

In many cases, the executives have no idea as to how information security can help their organization, so the main purpose of the policy is that the top management defines what it wants to achieve with information security.

The second purpose is to create a document that the executives will find easy to understand, and with which they will be able to control everything that is happening within the ISMS – they don’t need to know the details of, say, risk assessment, but they do need to know who is responsible for the ISMS, and what to expect from it.

For such information related documentation process visit: ISO 27001 Documents