Answer: Yes, ISO 27001 allows you to set the scope of your ISMS for only one part of your organization. However, this is not recommendable for smaller organizations (smaller than 100 employees) - this is because all parts of your organization that will be outside of the scope will be treated as an "outside world" which means you will need to protect the information within the ISMS scope from those departments which are outside of the scope.
However, many folks I work with often inquire about or request some form of attestation of compliance (e.g. not certification, but some form of attestation that they are compliant with the standard). My inquiry was more about that… Can anyone attest to 27001 compliance (internally or via a third party)? Perhaps a bit of a grey area…
Answer: Internal audit is mandatory according to ISO 27001, so this is something you must do - however this internal audit has no relevance for the outside world. For the third parties, only the ISO certificates issued by certification bodies are recognized.
I’m guessing in such cases it really boils down to the ‘opinion’ of the person / party providing the attestation and their willingness to stake their reputation on such a claim. Correct?
Answer: I would say this is primarily a question of credibility - if the "certificate" is issued by a company that has no license for performing the certification, who would trust them?
There is no particular part of the system that you have to be f ocusing on by default. You should pay special attention to the most complex processes and the ones in which the probability of spotting nonconformities is the highest.
Answer: Interesting question... in my opinion, it would be possible to coordinate the risk assessment and risk treatment process from a remote location, however I think that the following things would need to be done locally in the office for which the risk management is done:
- Listing all the assets, determining threats and vulnerabilities - this is because someone who is remote cannot be aware of all these elements
- Determining the impact and likelihood - again, the same explanation as above
- Implementing the controls - if we speak about physical controls that, of course, needs to be done locally; also all the technical controls (e.g. alarm systems and other hardware, locally installed software, etc.)
Somewhere halfway are organizational controls (e.g. policies, procedures, etc.) - of course, you can write all the documentation from a remote location, however the question is whether you can convince all the on-site employees to start using them? If your company culture allows this, then you would be able to do this, however there are not many companies who could succeed in such approach.
Answer:
There is no cookbook how to do it. COBIT is IT governance framework and ITIL is IT service management framework. You can see COBIT as interface between company (and its strategy, goals, risks...) and IT services. ITIL should enable excellence in management of your IT services (throughout their lifecycle) and COBIT should enable alignment of the IT organization with the goals of the business.
COBIT is much broader than ITIL and ITIL goes much more in details. Ideally, they are implemented together to integrate business and IT services.
Hazard analysis in iron steel making lan
Answer:
The process is the same regardless of the industry. First step in occupational hazard analysis is to determine the procedure for it that includes criteria for analysis that will tell you whether the hazard is significant or not. Then you need to conduct the analysis for each of the work places and see which are subjected to unacceptable hazards and what needs to be done to decrease the hazard and implement operational control.
Answer: Residual risk is the level of risk once you apply the controls - for example, if you had a risk that had a value of 9, and you applied controls so that impact and likelihood have decreased, then the level of residual risk could be e.g. 5.
Answer: The audit process is not prescribed by any standard, so you can do it any way you feel is appropriate. In most cases, ISMS is audited per controls, not per processes, although you can do it per processes as well.