Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Search results
11275 results
Guest
Guest
Create New Topic As guest or Sign in
Assign topic to the user
-
Information Security Policy
In the new ISO 27001:2013, clause 5.2 and A.5.1.1/A.5.1.2 controls are refer to the same thing: Information Security Policy. But, clause 5.2 describes the top-level Information security policy, while controls A.5.1.1 and A.5.1.2 speak about detailed security policies that cover certain areas of information security. Please, read this article for more information One information Security Policy, or several policies: https://advisera.com/27001academy/blog/2013/06/18/one-information-security-policy-or-several-policies/
What is your recommendation to record that employees were aware of the policies and other ISMS documents?
Answer:
There are several ways, but I recommend you to perform training sessions (inviting to all staff). In this sessions you can present the ISMS, requirements, documents, records, etc. For each session, you can have a physical document with signature of attendance of all people. After each session, also you can d evelop a small test to evaluate the awareness of each employee (their results is a evidence). If you need information on how to perform training and awareness for ISO 27001, please read this article How to perform training & awareness for ISO 27001 and ISO 22301: https://advisera.com/27001academy/blog/2014/05/19/how-to-perform-training-awareness-for-iso-27001-and-iso-22301/ -
Documented information
Yes, it is correct. There are some documents that are mandatory for the ISO 27001 (an example is the Access Control Policy, by the clause A.9.1.1). If you want to know the list of mandatory documents and records (remember that they are different things), you can read this article (also you can see non mandatory documents) List of mandatory documents required by ISO 27001 (2013 revision): https://advisera.com/27001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-27001-2013-revision/ -
Interested Parties need clarification of this. I'm looking for an example of a
The main point here is that you have to identify all interested parties (this is a requisite in the ISO 27001 4.2 a)). So, you need to answer this question: Who are interested parties?
You will find help about how identify interested parties at this article: "How to identify interested parties according to ISO 27001 and ISO 22301": https://advisera.com/27001academy/knowledgebase/how-to-identify-interested-parties-according-to-iso-27001-and-iso-22301// -
Documents and records
The first thing is that you have to differentiate between documents and records, they are not the same thing. A document can be a procedure, a methodology, a plan, etc. A record can be result of internal audit, result of management review, logs, etc. So, the difference is that a document describes actions, whereas a record is the result (and evidences for auditors) of actions performed.
Second thing, you have to read this article to know what are the list of mandatory documents and records that you need in the ISO 27001 (also you can see Non mandatory documents) List of mandatory documents required by ISO 27001 (2013 revision): https://advisera.com/27001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-27001-2013-revision/ -
Program Source Code
The control is not only for program source code, is also for associated items, such as designs, specifications, verifications plans and validation plans. It means that you need to control the access to them. This can be achieved by controlled central storage of such code (assigning privileges in a network folder, or in a file server, or in a repository of code with user/password). Also you have to be careful with the libraries, which should not be held in operational systems (furthermore you need also control access to them). -
ISO 27001:2013 Asset Based Risk Assessment
If you have Asset based RA, I suppose that you have implemented the ISO 27001:2005 (old version). If so, you current methodology is accepted by the new version ISO 27001:2013, therefore you do not need to make changes. You can see the main changes of the ISO 27001:2013 at this article What has changed in risk assessment in ISO 27001:2013: https://advisera.com/27001academy/knowledgebase/what-has-changed-in-risk-assessment-in-iso-270012013/
Also, if you need to develop a new methodology accepted by ISO 27001:2013, I recommend you to read this article How to write ISO 27001 risk assessment methodology": https://advisera.com/27001academy/knowledgebase/write-iso-27001-risk-assessment-methodology/
Finally, you can use our ISO 27001/ISO 22301 Risk Assessment Toolkit. Remember t hat you can download a free version if you click on the Free Demo tab: https://advisera.com/27001academy/iso-27001-22301-risk-assessment-toolkit/ -
Interested parties
Effectively, you have to identify all interested parties (employee, customers, but also suppliers and partners, shareholders, etc) affected by the scope of the ISO 27001. To do this task, this article will be very useful for you, please read it and if you have another question, ask us How to identify interested parties according to ISO 27001 and ISO 22301": https://advisera.com/27001academy/knowledgebase/how-to-identify-interested-parties-according-to-iso-27001-and-iso-22301// -
Incident Handling Procedure and Business Continuity Plan
If an incident occurs and need to resolve a danger immediately, execute the Incident Handling Procedure. After that, if there is a business disrupt, execute the Business Continuity Plan.
In accordance with the official definition of the ISO 22301-Business Continuity Management Systems, an incident is a situation that might be, or could lead to, a disruption, loss, emergency or crisis. On the other hand, in the standard there is no official definition for disaster, but we can consider that is the same or similar to a crisis or emergency. So, an incident can result in a disaster.
Generally, Disaster is related to the concept Disaster Recovery (technology), which is not the same that "Business Continuity" (whole organization). If you want to know the differences about this, please read this article Disaster recovery vs Business Continuity": https://advisera.com/27001academy/blog/2010/11/04/disaster-recovery-vs-business-continuity/ -
Difference between Incident and Disaster
In accordance with the official definition of the ISO 22301-Business Continuity Management Systems, an incident is a situation that might be, or could lead to, a disruption, loss, emergency or crisis. On the other hand, in the standard there is no official definition for disaster, but we can consider that is the same or similar to a crisis or emergency. So, an incident can result in a disaster.
Generally, Disaster is related to the concept Disaster Recovery (technology), which is not the same that "Business Continuity" (whole organization). If you want to know the differences about this, please read this article Disaster recovery vs Business Continuity": https://advisera.com/27001academy/blog/2010/11/04/disaster-recovery-vs-business-continuity/ -
ISO 27001, Alcance de la implementacion
Los términos y definiciones están incluidos en la ISO 27000 (no en la ISO 27001), y no existe una definición oficial para el término "organización", pero lo importante aquí es el alcance de la ISO 27001, el cual puede afectar a toda la organización o sólo a una parte. Por tanto, sí, se puede definir el alcance de la ISO 27001 para sólo una parte.
Por último, si quieres definir el alcance de la ISO 27001, este artículo te resultará muy útil:
https://advisera.com/27001academy/knowledgebase/how-to-define-the-isms-scope/