In keeping with the journal of international security, it is now time to implement the WSIS. And for that, there are less than a year since the ISO 27003 standard, dedicated to the implementation of an ISMS.
As the ISO 27002 standards and all that follow, this is a guide and not a requirement. The main idea is to establish a WSIS in building a project . It is indeed to determine the tasks to be performed and to properly synchronize the time and resources to engage each of them.
We will explore this through its standard clauses 5-9 we provide guidelines for starting a project to WSIS 5 phases so that follow a logical order. However, the standard will not provide any indication to sustain the system of management in question once launched.
This is how the standard ...
Clause 5: Obtain the agreement of management to initiate the draft WSIS
The purpose of this clause is twofold: to obtain the agreement of management and write a first draft of Planning Policy Project. Specifically, this clause was intended to define the needs for security and business objectives to determine the direction and scope to be involved in the WSIS. This will be achieved through three sub-steps:
Clause 6: Define the scope of the WSIS, its limits and the politics of WSIS
For those who are interested in ISO 27001, we find here two documents required by it. Remember that ISO 27001 is assigned to a specific perimeter. This therefore an important component. As for the policy of the WSIS, it will represent the vector of development throughout the project. Five sub-steps are needed this time:
Clause 7: Analyze the prerequisite security
Quite simply, this is to establish an inventory of the perimeter for security. The results of this analysis will help us better understand the actions to be taken thereafter. To obtain this information, 3 sub-steps are proposed:
Clause 8: Conduct a risk analysis and prepare a treatment plan risk
These elements are required by ISO 27001, in the flat phase. To carry out this part of the project, we can build on the ISO 27005 standard that we will see in episode 5 of our study. The key steps in our project for the 8th clause:
is the last step so that our Policy is ready and able to return and principal phase of our PDCA. 4 sub-steps should be taken into account this time:
To be more precise ...
The standard provides in its appendices of useful information to clarify the issues raised in the body of the standard and especially help the implementer. Here are the schedules and the purpose of each:
We will explore this through its standard clauses 5-9 we provide guidelines for starting a project to WSIS 5 phases so that follow a logical order. However, the standard will not provide any indication to sustain the system of management in question once launched.
This is how the standard ...
Clause 5: Obtain the agreement of management to initiate the draft WSIS
The purpose of this clause is twofold: to obtain the agreement of management and write a first draft of Planning Policy Project. Specifically, this clause was intended to define the needs for security and business objectives to determine the direction and scope to be involved in the WSIS. This will be achieved through three sub-steps:
- Clarify priorities that lead to the deployment of WSIS
- Define the scope of future preliminary WSIS
- Making a plan business and planning the project for approval .
Clause 6: Define the scope of the WSIS, its limits and the politics of WSIS
For those who are interested in ISO 27001, we find here two documents required by it. Remember that ISO 27001 is assigned to a specific perimeter. This therefore an important component. As for the policy of the WSIS, it will represent the vector of development throughout the project. Five sub-steps are needed this time:
- Define the scope of organization and its limits in terms (eg managers and people involved in the project);
- Define the scope and limitations IT (eg software, servers, technologies ...);
- Define the scope and limits physical (eg sites that will be part of the perimeter);
- Synthesize the three previous steps to define the overall scope and final with its limitations (Note: any exclusion must be justified);
- Write the WSIS policy and make validate .
Clause 7: Analyze the prerequisite security
Quite simply, this is to establish an inventory of the perimeter for security. The results of this analysis will help us better understand the actions to be taken thereafter. To obtain this information, 3 sub-steps are proposed:
- Define prerequisites for process safety on WSIS (critical processes? Legal constraints? Priority goods? Vulnerabilities involved? Need for awareness and training?) ;
- property Set within the perimeter of the WSIS (classification of goods and needs from the previous step);
- Assess security level (using an audit compliance (eg ISO 27002) and results of previous audits).
Clause 8: Conduct a risk analysis and prepare a treatment plan risk
These elements are required by ISO 27001, in the flat phase. To carry out this part of the project, we can build on the ISO 27005 standard that we will see in episode 5 of our study. The key steps in our project for the 8th clause:
- Conduct a risk analysis (Please provide the methodology and results);
- Select control objectives and controls themselves (writing the statement of applicability and the treatment plan risk, cf. Appendix A of ISO 27001);
- Obtain management approval for implementation and maintenance of the WSIS (must contain the acceptance level for the residual risk).
is the last step so that our Policy is ready and able to return and principal phase of our PDCA. 4 sub-steps should be taken into account this time:
- Designing the final safety organization (roles and responsibilities involved, Document Management Policy, Safety Policy);
- Design IT operations and physical (implementation and monitoring of security measures in defining each task and assigning them to a manager);
- Design specific tasks a WSIS (WSIS as management planning management review, training and user awareness, records for checking and improving the ISMS);
- Produce final schedule of the project WSIS (describe all the tasks and methods associated with assigning a responsible (under the first stage) for each task identified (2nd and 3rd sub-steps).
To be more precise ...
The standard provides in its appendices of useful information to clarify the issues raised in the body of the standard and especially help the implementer. Here are the schedules and the purpose of each:
- Appendix A: checklist of tasks to achieve correspondence with ISO 27003 / ISO 27001;
- Appendix B: Roles and Responsibilities Safety Information (to help the organization);
- Appendix C: Information about the internal audit (Reminder: Clause 6 of ISO 27001);
- Appendix D: Structure policies (hierarchy of policies and procedures and sample policy);
- Appendix E: Monitoring WSIS ( establishment and operation of indicators, cf. ISO 27004).
0 comments:
Post a Comment