Search in ISMS Guides


Tuesday, July 24, 2007

3. Organization of information security (ISO)

Internal organization

The objective of this category is to manage information security within the organization's overall administrative structure.

Management commitment to information security • Management at all levels should actively support security within the organization with clear direction, demonstrated commitment, and explicit acknowledgement of information security responsibilities. Control includes:

  • clear direction and visible support for information security initiatives, including providing appropriate resources for information security controls;
  • coordination of information security efforts across the organization, including designation of information security officer(s)and committee(s);
  • assuring formulation, review and approval of appropriate organization-wide information security policy;
  • periodic reviews of the effectiveness of information security policy, including external review as appropriate, and updating of the policy as needed; and
  • appropriate management controls over new information facilities, systems and capabilities.

Authorities: ISO-27002:2005 6.1.1.

Information security coordination • Information security activities should be coordinated by representatives from different parts of the organization with relevant roles and job functions. Control includes:

  • assessing adequacy and coordinating implementation of controls;
  • ensuring that information security controls are executed in compliance with information security policy;
  • proposing methodologies and processes (e.g., risk assessment) subject to management approval;
  • evaluating security incident data from across the organization, and recommending appropriate action;
  • identifying significant threat and vulnerability changes, and recommending appropriate action; and
  • promoting security awareness and training throughout the organization.

Authorities: ISO-27002:2005 6.1.2.

Allocation of information security responsibilities • All information security responsibilities should be clearly defined. Control includes:

  • identification and clear definition of assets and security controls for each information facility; and
  • identification of the individual responsible for security for each information facility.

Authorities: ISO-27002:2005 6.1.3.; HIPAA 164.308(a)(2);

Authorization process for information processing facilities • A management authorization process for new information processing facilities and capabilities should be defined and implemented. Control includes:

  • formal approval of purpose and use for each new system, or for existing systems that are materially changed;
  • certification that hardware/software used by the new (or changed) system meets organizational standards,
  • approval of any non-standard functions, locations, or users, including approval of any personal or privately-owned hardware/software/facilities to be used; and
  • certification that the new (or changed) system complies with all applicable security controls.

Authorities: ISO-27002:2005 6.1.4.

Confidentiality agreements • Requirements for confidentiality and non-disclosure agreements (NDA) should reflect the organization's needs for protection of information. Such agreements should be periodically reviewed. This control includes . Control includes specification of:

  • definition of the information, information type(s) or information system(s) to be protected;
  • confidentiality requirements for that information, in clear, legally-enforceable terms, that accord with all relevant statutory-regulatory and private certificatory authorities;
  • responsibilities of signatories, including limitations on use or disclosure of information and adherence to security controls;
  • terms of ownership of information, including any trade secret or intellectual property requirements;
  • expected duration of the agreement;
  • required actions when the agreement is terminated, including requirements to return or destroy information;
  • right to monitor compliance with the agreement;
  • processes for reporting of and notice of breaches; and
  • expected actions to be taken in the event of a breach.

Authorities: ISO-27002:2005 6.1.5.

Contact with authorities • Appropriate contacts with relevant external authorities should be maintained. Control includes:

  • development of policies, procedures and contact lists that specify when and by whom external authorities should be contacted;
  • specification of the timing and manner in which breaches shall be reported, to ensure appropriate reporting.

Authorities: ISO-27002:2005 6.1.6.

Contact with special interest groups • Appropriate contacts with special interest groups or other specialist security forums and professional associations should be maintained.

Authorities: ISO-27002:2005 6.1.7.

Independent review of information security • The organization's approach to managing information security and its implementation should be reviewed independently at planned intervals, and when there are significant changes to internal structure or the external environment.

Authorities: ISO-27002:2005 6.1.8.

External parties

This category aims to maintain the security of the organization's information and information processing facilities that are accessed, processed, communicated to or managed by external parties.

Identification of risks related to external parties • Risks to the organization's information and information processing facilities from business processes involving external parties should be identified and appropriate controls implemented before granting access. Control includes:

  • a risk assessment to identify any requirements for specific controls, taking into account characteristics of external users, their type of access, and the value and sensitivity of the information involved;
  • contractual specification of the terms and conditions of access, including required security controls;
  • implementation of all security controls before access is permitted;

Authorities: ISO-27002:2005 6.2.1.

Addressing security when dealing with customers • All identified security requirements should be addressed before giving customers access to the organization's information or assets. Controls considerations are similar to those for external parties.

Authorities: ISO-27002:2005 6.2.2.

Addressing security in third party agreements • Agreements with third parties involving accessing, processing, communicating or managing the organization's information or information processing facilities should cover all relevant security requirements. Control includes specifying security requirements related to:

  • the applicable information security policy or policies;
  • necessary controls to ensure asset protection;
  • user and system administrator awareness and training efforts;
  • responsibilities related to hardware/software selection and configuration;
  • a clear and specific process of change management;
  • agreements for reporting, notification and investigation;
  • reporting structure and reporting formats;
  • levels of acceptable/unacceptable service and service continuity;
  • definitions of verifiable performance criteria;
  • rights to monitor and audit activities;
  • problem resolution processes, including escalation steps;
  • intellectual property rights and ownership of data;
  • policies regarding subcontractors; and
  • conditions for renegotiation/termination.

Authorities: ISO-27002:2005 6.2.3.; HIPAA 164.308(b)(1)

Article By :

No comments: