Understanding the organization -infosavvy

ISO 27001 Implementation Guidelines clause 4.1

ISO 27001 Implementation Guidelines clause 4.1, this concept would be clear over here through this article etc.

Understanding the organization and its context

Required activity

The organization determines external and internal issues relevant to its purpose and affecting its ability to realize the intended outcome(s) of the knowledge security management system (ISMS).

Explanation
As an integral function of the ISMS, the organization continually analyses itself and therefore the world surrounding it. This analysis cares with external and internal issues that in how affect information security and the way information security are often managed, which are relevant to the organization’s objectives.

Analysis of those issues has three purposes:
— Understanding the context so as to make a decision the scope of the ISMS;
— Analyzing the context so as to work out risks and opportunities;
— Ensuring that the ISMS is tailored to changing external and internal issues.
External issues are those outside of the organization’s control. this is often mentioned because the organization’s environment.

Analyzing this environment can include the subsequent aspects:
a) Social and cultural;
b) Political, legal, normative and regulatory;
c) Financial and macroeconomic;
d) Technological;
e) Natural;
f) Competitive.
These aspects of the organization’s environment continually present issues that affect information security and the way information security are often managed. The relevant external issues depend upon the organization’s specific priorities and situation.

For example, external issues for a selected organization can include:
a) The legal implications of using an outsourced IT service (legal aspect);
b) Characteristics of the character in terms of possibility of disasters like fire, flood and earthquakes (natural aspect);
c) Technical advances of hacking tools and use of cryptography (technological aspect); and
d) The overall demand for the organization’s services (social, cultural or financial aspects).
e) Internal issues are subject to the organization’s control.

Analyzing the interior issues can include the following aspects:
a) The organization’s culture;
b) Policies, objectives, and therefore the strategies to realize them;
c) Governance, organizational structure, roles and responsibilities;
d) Standards, guidelines and models adopted by the organization;
e) Contractual relationships which will directly affect the organization’s processes included within the scope of the ISMS;
f) Processes and procedures;
g) The capabilities, in terms of resources and knowledge (e.g. capital, time, persons, processes, systems and technologies);
h) Physical infrastructure and environment;
i) Information systems, information flows and deciding processes (both formal and informal);
j) Previous audits and former risk assessment results.

Based on an understanding of the organization’s purpose (e.g. pertaining to its mission statement or business plan) also because the intended outcome(s) of the organization’s ISMS, the organization should:
— Review the external environment to spot relevant external issues; and review the interior aspects to spot relevant internal issues. In order to spot relevant issues, the subsequent question are often asked:

How does a particular category of issues affect information security objectives?

Three samples of internal issues function an illustration by:

Example 1 on governance and organizational structure ; When establishing an ISMS, already existing governance and organizational structures should be taken under consideration . As an example, the organization can model the structure of its ISMS supported the structure of other existing management systems, and may combine common functions, like management review and auditing.

Example 2 on policy, objectives and methods :An analysis of existing policies, objectives and methods , can indicate what the organization intends to realize and the way the knowledge security objectives are often aligned with business objectives to make sure successful outcomes.

Example 3 on information systems and knowledge flows :When determining internal issues, the organization should identify, at a sufficient level of detail, the knowledge flows between its various information systems.
As both the external and therefore the internal issues will change over time, the problems and their influence on the scope, constraints and requirements of the ISMS should be reviewed regularly. Documented information on this activity and its outcome is mandatory only within the form and to the extent that the organization determines as necessary for the effectiveness of its management system.

Questions related to this topic

  1. Explain ISO 27001 Implementation Guidelines clause 4.1?
  2. What are the five goals of information security governance?
  3. What are the security governance principles?
  4. WHAT IS IT governance and why is it important to an organization?
  5. Why is information security governance important?

ISO 27001 Requirements


Clause 4.4 Information security management system
Clause 4.3 Determining the scope of the information security management system
Clause 5.1 Leadership and commitment
Clause 5.2 Policy
Clause 5.3 Organizational roles, responsibilities and authorities 
Clause 6.1 Actions to address risks and opportunities
Clause 6.1.2 Information security risk assessment process
Clause 6.1.3 Information security risk treatment
Clause 6.2 Information security objectives & planning
Clause 7.1 Resources
Clause 7.2 Competence
Clause 7.3 Awareness
Clause 7.4 Communication
Clause 7.5 Documented information Implementation Guideline
Clause 8.1 Operational planning & control
Clause 8.2 Information security risk assessment
Clause 8.3 Information security risk treatment
Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation
Clause 9.2 Internal audit
Clause 9.3 Management review
Clause 10.1 Non conformity and corrective action
Clause 10.2 Continual Improvement 

ISO 27001 Annex A Controls


Annex A.5 Information Security Policies
Annex A.6 Organization of Information Security
Annex A.6.2 Mobile Devices and Teleworking
Annex A.7 Human Resource Security
Annex A.7.2 During Employment
Annex A.7.3 Termination and Change of Employment
Annex A.8 Asset Management
Annex A.8.1.3 Acceptable Use of Assets & A.8.1.4 Return of Assets
Annex A.8.2 Information Classification
Annex A.8.2.2 Labeling of Information & A.8.2.3 Handling of Assets
Annex A.8.3 Media Handling
Annex A.9 Access Control
Annex A.9.1.2 Access to Networks and Network Services
Annex A.9.2 User Access Management
Annex A.9.2.3 Management of Privileged Access Rights  
Annex A.9.2.4 Management of Secret Authentication Information of Users
Annex A.9.2.5 Review of User Access Rights 
Annex A.9.2.6 Removal or Adjustment of Access Rights
Annex A.9.3 User Responsibilities
Annex A.9.4 System and Application Access Control
Annex A.9.4.4 Use of Privileged Utility Programs 
Annex A.9.4.5 Access Control to Program Source Code
Annex A.10 Cryptography
Annex A.11 Physical and Environmental Security
Annex A.11.2 Equipment
Annex A.11.1.3 Securing Offices, Rooms and Facilities
Annex A.11.1.4 Protecting Against External and Environmental Threats
Annex A.11.1.5 Working in Secure Areas
Annex A.11.1.6 Delivery and Loading Areas
Annex A.11.2.4 Equipment Maintenance
Annex A.11.2.5 Removal of Assets
Annex A.11.2.6 Security of Kit and Assets Off-Premises
Annex A.11.2.7 Secure Disposal or Re-use of Equipment
Annex A.11.2.8 Unattended User Equipment
Annex A.11.2.9 Clear Desk and Clear Screen Policy
Annex A.12 Operations Security
Annex A.12.2 Protection from Malware
Annex A.12.3 Backup
Annex A.12.4 Logging and Monitoring
Annex A.12.5 Control of Operational Software
Annex A.12.6 Technical Vulnerability Management
Annex A.12.7 Information Systems Audit Considerations
Annex A.13 Communications Security
Annex A.13.2 Information Transfer
Annex A.13.2.3 Electronic Messaging
Annex A.13.2.4 Confidentiality or Non-Disclosure Agreements
Annex 14 System Acquisition, Development and Maintenance
Annex A.14.1.2 Securing Application Services on Public Networks
Annex A.14.1.3 Protecting Application Services Transactions
Annex A.14.2 Security in Development and Support Processes
Annex A.14.2.3 Technical Review of Applications after Operating Platform Changes
Annex A.14.2.4 Restrictions on Changes to Software Packages
Annex A.14.2.5 Secure System Engineering Principles
Annex A.14.2.6 Secure Development Environment
Annex A.14.2.7 Outsourced Development
Annex A.14.2.8 System Security Testing
Annex A.14.2.9 System Acceptance Testing
Annex A.14.3 Test data
Annex A.15 Supplier Relationships
Annex A.15.1.2 Addressing Security Within Supplier Agreements
Annex A.15.1.3 Information and Communication Technology Supply Chain
Annex A.15.2 Supplier Service Delivery Management
Annex A.16 Information Security Incident Management
Annex A.16.1.2 Reporting Information Security Events
Annex A.16.1.3 Reporting Information Security Weaknesses
Annex A.16.1.4 Assessment of and Decision on Information Security Events
Annex A.16.1.5 Response to Information Security Incidents
Annex A.16.1.6 Learning from Information Security Incidents
Annex A.16.1.7 Collection of Evidence
Annex A.17 Information Security Aspects of Business Continuity Management
Annex A.17.1.3 Verify, Review and Evaluate Information Security Continuity
Annex A.18 Compliance
Annex A.18.1.3 Protection of Records
Annex A.18.1.4 Privacy and Protection of Personally Identifiable Information
Annex A.18.1.5 Regulation of Cryptographic Controls
Annex 18.2 Information Security Reviews

 

About ISO 27002



This Blog Article is posted by

Infosavvy, 2nd Floor, Sai Niketan, Chandavalkar Road Opp. Gora Gandhi Hotel, Above Jumbo King, beside Speakwell Institute, Borivali West, Mumbai, Maharashtra 400092

Contact us – www.info-savvy.com

Leave a Comment