Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Search results
11270 results
Guest
Guest
Create New Topic As guest or Sign in
Assign topic to the user
-
Information classification
To me CUG is for a select number of people in say a committee and confidential is for say the person that the information has been sent to only.
In your opinion, is the difference correct, if not, why not and do you believe CUG is a useful classification to continue with or just use confidential?
Answer:
Yes, in my opinion it is correct, although you can also add a lower confidentiality level (for example Public"). For more information, please read this article: "Information classification according to ISO 27001": https://www.iso27001standard.com/blog/2014/05/12/i************************************************* -
Page policy document on context of the organization
If you are referring to the clause 4.1 Understanding the organization and its context of the ISO 27001:2013, this article will help you, please read it Explanation of ISO 27001:2013 clause 4.1 (Understanding the organization) : https://advisera.com/27001academy/knowledgebase/how-to-define-context-of-the-organization-according-to-iso-27001/ -
Information technology and Risk management
It is so because for example if you have a disk drive without data or without information, there are no risks related to the information security (you only have technology), so the risk management in this case it is not necessary. -
Information Security in Project Management and Legal aspects
2) What are the legal aspects I should be looking for a mid sized IT services company.
Answer:
1) As you know, it is related with the control A.6.1.5, and to implement it you can do this in your organization: a) Include information security objectives in project objectives, b) Perform an information security risk assessment at an early stage of the project to identify necessary controls and c) information security is part of all phases of the applied project methodology.
2) Depends of you country, but common laws (at least in Europe) are related with the protection of personal data, intellectual property and electronic signature. To know more information about the laws regulation in each country, please see this List of legal, regulatory, contractual and other requirements" : https://www.infosecpedia.info/laws-regulatio******************************************* -
ISO 27002 certification
I think so, because the ISO 27002:2013 has 114 security controls, and most of them are directly related with technology (Cryptography, Operations security, Communications security, etc). Therefore this certification can help you to prove that you have good knowledge about an International standard which is composed with security controls, many technological. Furthermore, probably with your skills I think that will be very easy to you to pass the exam.
Finally also keep in mind that personal certificates can help your companys ISMS, if you want to know more about this, please read this article How personal certificates can help your companys ISMS : https://advisera.com/27001academy/blog/2014/10/06/how-personal-certificates-can-help-companys-isms/ -
Becoming ISO 27001 auditor
Sorry but we are not sure if you are interested in internal audits or certification audits. The Auditor training course is very recommendable for both, but also is necessary to have experience in the standard (as minimal as a junior consultant). In the case of internal audit, the pay rate depends of your experience and also depends of the company that you want to audit and her location (there are countries where the pay/rate is lower for any job). In the case of the certification audit the pay rate depends of the certification body, and here also your experience will be very important. So, while more experience you have, it will be more easy to you find jobs as auditor, and your pay rate will be higher.
If you want to become an ISO 27001 internal auditor, please read this article Qualifications for an ISO 27001 Internal Auditor: https://advisera.com/27001academy/blog/2015/03/30/qualifications-for-an-iso-27001-internal-auditor/
Also you can read this article How to become ISO 27001 Lead Auditor : https://advisera.com/27001academy/knowledgebase/how-to-become-iso-27001-lead-auditor/ -
Clauses 4.1 and 4.4
There are no templates for clauses 4.1 and 4.4 because it is not mandatory. Keep in mind that only is mandatory if the standard establishes it. Example: You can see at the end of clause 4.3 The scope shall be available as documented information. And as you know, we have a template for this in the folder "03 ISMS Scope Document.
Remember that you can see the list of mandatory documents here 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/
Also you can read this article "Explanation of ISO 27001:2013 clause 4.1 (Understanding the organization)": https://advisera.com/27001academy/knowledgebase/how-to-define-context-of-the-organization-according-to-iso-27001/ -
Structure of the Risk Treatment Plan
ISO 27001 does not prescribe the structure of the Risk Treatment Plan, but if you follow the logic of clause 6.2, then you should include the following information: what to implement, by whom, when, using which resources, etc. You can see a preview of the Risk treatment plan here (look for the "Free Demo" tab): https://advisera.com/27001academy/documentation/risk-treatment-plan/
In my opinion, the best would be to organize the Risk treatment plan according to controls - first of all RTP is based on Statement of Applicability (which is also based on controls), and second the implementation will be much easier if the planning is done control by control.
Read also this article: Risk Treatment Plan and risk treatment process Whats the difference? https://advisera.com/27001academy/iso-27001-risk-assessment-treatment-management/#treatment -
Quick Risk assessment
No, it is not correct, and it is not a control in the ISO: The System shall have a logoff button. One way to perform the risk assessment (although you can develop your own methodology): a.- Identify assets (software can be a type of asset, and an app can be an asset), b.- Identify threats related to the assets (you can do it with a catalogue), c.- Calculate risks (based on impact and likelihood). If the risk is below a level defined by the organization, it is acceptable, and there is no problem (current controls for the asset are sufficient). If the risk is above, then the organization must to apply controls to reduce it to an acceptable level. What controls? The defin ed in the Annex A of the ISO 27001.
I recommend you to read these articles:
How to write ISO 27001 risk assessment methodology : https://advisera.com/27001academy/knowledgebase/write-iso-27001-risk-assessment-methodology/
ISO 27001 risk assessment: How to match assets, threats and vulnerabilities : https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-how-to-match-assets-threats-and-vulnerabilities/
Finally, here there is a free webinar that I think that can be very interesting for you The basics of risk assessment and treatment according to ISO 27001 : https://advisera.com/27001academy/webinar/basics-risk-assessment-treatment-according-iso-27001-free-webinar-demand/ -
Business Continuity
Yes, we have a template that can help you. Please see this (try our free version clicking on Free Demo tab) : https://advisera.com/27001academy/blog/2010/04/08/how-to-write-business-continuity-plans/
Also read this article How to write business continuity plans? : https://advisera.com/27001academy/blog/2010/04/08/how-to-write-business-continuity-plans/
And also, can be very interesting for you this free webinar ISO 22301 Foundations Part 3: Business Continuity Planning" : https://advisera.com/27001academy/webinar/implementing-business-impact-analysis-according-to-iso-22301-free-webinar/
Finally, keep in mind that the ISO 22301 is focused on Business Continuity Management, and it is more detailed for the Business Con tinuity Plan, so we can use it as reference for the development of the Business Continuity Plan required by A.17 ISO 27001