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
-
Implementation guidance ISO 27002
Let me put an example: Based on our risk evaluation we have determined that control 9.4.2 Secure log-on procedures, applies. In our Control Access Policy we have try to follow the implementation guidance for control 9.4.2, as indicated in ISO/IEC 27002:2013, but we can not comply with some requisites. Taking into account that the standard says that a good log-on procedure should, not a good log-on procedure must, we think we are right.
Can we have some problem with certification audit?
Answer:
You are right, ISO 27002 is not mandatory, this is only the guideline. You do not have to apply everything that is written in ISO 27002; you have to apply only what ISO 27001 requires of you.
Unfortunately, sometimes the certification auditors look towards ISO 27002, but you can clear this out very easily with them - simply ask them whether th ey think ISO 27002 is mandatory or not.
This article will help you: ISO 27001 vs. ISO 27002: https://advisera.com/27001academy/knowledgebase/iso-27001-vs-iso-27002/ -
Is equipment in data center to be considered as assets or controls?
Answer:
Theoretically, you could consider this equipment as controls only, but to be on the safe side you should consider them as assets, because that way you will be able to assess the risks related to them in a much better way.
For instance, if you considered power generator as an asset, through the risk assessment you might realize that it is not regularly maintained, that the people operating it are not trained, etc. - you probably wouldn't realize such information if you considered the power generator only as a control. -
Definition of asset in ISO/IEC 27000:2014
Answer:
It is true that ISO 27000:2014 does not have a specific definition in clause 2 (Terms and definitions), however it does give an explanation on what assets are in clause 3.1.
By the way, ISO 27000 uses the term "assets" very often in its text, so obviously this term is still very important for the concept of information security. -
Asset owner for the personnel
Answer:
I assume you refer to "personnel" as an asset. In such case, the asset owner is the superior manager of each particular employee. For example, for the employee in the accounting department, the asset owner is the head of the accounting department. -
Does the Impact Reduce When applying Controls
Actually, you have hit the core of the issue with risk assessment and treatment - theoretically, the controls can reduce both the impact and the likelihood, but in 99% of the cases they will reduce only the likelihood.
Here's an example where the control will reduce both the impact and the likelihood:
Asset: database
Threat: electricity outage
Vulnerability: no alternative power source
Control: implement UPS.
With the implementation of intelligent uninterruptible power supply (that will shut down the server once its battery is almost empty) not only will the likelihood reduce, but also the impact because the server will be shut down in a controllable fashion, which means the database integrity will be preserved. -
Information security policy vs. Acceptable use policy
ISO 27001 is not very clear when it comes to this question. However, best practice is the following: Information security policy should be a short top-level document that describes general approach of a company towards information security; Acceptable use policy should be a longer document describing all the security rules that are applicable to all employees.
These articles will also help you:
Information security policy how detailed should it be? https://advisera.com/27001academy/blog/2010/05/26/information-security-policy-how-detailed-should-it-be/
How to structure the documents for ISO 27001 Annex A controls https://advisera.com/27001academy/blog/2014/11/03/how-to-structure-the-documents-for-iso-27001-annex-a-controls/ -
Licensed software in ISO 27001
Answer:
ISO 27001 says that you have to comply with your local laws and regulations; and I'm sure that each country in the world has laws which say that pirated versions of software are illegal. -
Information and Classification Policy
Yes, ISO 27001 allows you to use any classification levels you find appropriate.
Example - client confidential covers Client data contained or created using our application software or custom reports created with database tools, Email communications with clients, etc. Is this kind of classification acceptable?
Answer: You should not prescribe the classification levels for particular information in advance - asset owners should decide on classification levels once they assess the confidentiality of particular information in question.
It would be a bit of a complication to label some of the information, so is it acceptable to prescribe that they are not labeled? Just to believe that awareness would be enough?
Answer: Theoretically this is possible, but it is not really recommendable. The problem is the following: if you prescribe that all the information is classi fied if unlabeled, then you are always in danger that someone did not know for this rule.
Should we classify information by the most important one from the group - for the most of the contracts with clients there is the same level of confidentiality, but there is always a couple of them which are super, top level confidential. Should we, because of this, classify all the contracts as top level confidential?
Answer: Probably the best approach in this situation is to classify different contracts with different level of confidentiality.
By the way, this article will help you: Information classification according to ISO 27001 https://advisera.com/27001academy/blog/2014/05/12/information-classification-according-to-iso-27001/ -
Policy Version Control
For your Information security incident management policy I think it would be better to continue from the old version number - this is because your policy is not a new one, it has a continuity from the old policy that existed before the merger with the QMS document. -
Difference between clauses 5.1.e and 6.1.1.a of ISO 27001:2013
Answer:
Both clauses you refer to have the same text, however clause 5.1 e) refers to the responsibilities of the top management, while clause 6.1.1 a) refers to anyone who performs the planning of the ISMS.