First step in the integration process is to identify all common requiremnets of both standards and start with implementing them first, and then you need to focus on specific requiremnets of ISO 14001 and OHSAS 18001.
For example, the common requiremnets are control of documents and records, policies, objectives, competence and awareness, communication, nonconformities, corrective actions, internal audit etc.
Answer: To ensure you identify the most relevant risks related to an asset (you do not have to identify all risk), you should ensure an approach from as many points of view as possible. Think about including in the same risk identification session people from different areas and processes. For example, if you are evaluating sales process, try to bring in people from IT, financial and legal department. For sure all of them will have different interest on information security and will point out different risks.
And even if you didn't identify all the risks, you will probably identify them during the next review of your risk assessment - no one expects you to do it perfectly the first time, risk assessment is something that is continually improved.
La norma ISO 14001 requiere a las organizaciones definir el contexto de la organización mediante la determinación de cuestiones internas y externas que son relevantes para sus objetivos y que afectan la capacidad de alcanzar los resultados esperados en su SGA. Este término de "resultados esperados" se refiere a lo que es requerido de la organización y lo que quiere alcanzar implementando el SGA. Los resultados mínimos previstos bajo el estándar incluyen la mejora del desempeño ambiental, el cumplimiento de las obligaciones legales y con los objetivos ambientales
Puedes llevar a cabo un análisis DOFA o un análisis PEST a la hora de determinar el contexto de la organización, o programar una sesión de tormenta de ideas con el personal relevante de tu organización. Los resultados de esos análisis o un registro con los minutos de la sesión de tormenta de ideas probarán que se han considerado todas las cuestiones dentro del SGA.
Además es posible determinar qué partes de la organización deberían de formar parte del SGA dependiendo de las razones para la implementación de la norma, por ejemplo si se trata de un requerimiento del consumidor o si es un requerimiento de la propia compañía.
NIST, COSO and ISO 27001
Answer: In fact these frameworks are not competitors, but they complement each other. COSO gives you a corporate view for risk management, and NIST SP 800 series provides security practices for IT environments. As for ISO 27001, it provides you a framework for managing information security, considering not only IT environments, but also physical and human aspects, as well as business objectives.
That said, while ISO 27001 is more prepared to manage information security than NIST standards and COSO, it can benefit form the other two frameworks for complementing its approach regarding IT controls and understanding of risk in business context.
These articles will provide you further explanation about these frameworks:
- How to integrate COSO, COBIT, and ISO 27001 frameworks https://advisera.com/27001academy/blog/2016/10/10/how-to-integrate-coso-cobit-and-iso-27001-frameworks/
- How to use the NIST SP800 series of standards for ISO 27001 implementation h ttps://advisera.com/27001academy/blog/2016/05/02/how-to-use-the-nist-sp800-series-of-standards-for-iso-27001-implementation/
Career on Information Security
I want to take up training and certification for ISO27001, and gradually move up ladder with CISA .
Here is dilemma like should i opt for ISO certification at this stage or not . And what approach to follow to attain same . What study material should i follow , do you take up training session, what action plan should i follow since post this data center project , there is high probability i would be aligned to different project for same role.
As of now i am finding myself in a situation while taking up decisions, since the decisions i take , my team would have to live with them for long . My self dont have prior experience in this domain and finding bit difficult to gauge CIA parameters.
I have expertise in Service operations , Incident , Change and Event management . Good knowledge of Serve r admin role and basics of network .
Answer: By what you described, my suggestion for your development would be first to consider obtaining knowledge on the requirements of the standard and how to conduct an implementation process. For that you can find on market ISO 27001 Lead implementation courses. Your previous knowledge on ITIL, servers administration and network will help, but information security covers much more issues, like human resources and legal requirements.
Second would be obtaining knowledge on audit aspects of ISO 27001, and for that you can consider either ISO 27001 Internal audit courses or ISO 27001 Lead auditor courses (for immediate or low budget you can go for internal audit courses, but since you are thinking about CISA, the lead auditor course can help you more regarding that goal).
Answer: For creation of a risk assessment you should consider:
- Definition of how to identify the risks to information security
- Definition of how to identify risk owners
- Definition of criteria for assessing consequences and likelihood of the risk
- Definition of how calculate the risk
- Definition of criteria for accepting risks
Regarding the risk analysis, the main approaches are qualitative and quantitative analysis
How can I define the Scope of the EMS for a manufacturing company, according to 2015 version of ISO 14001, without going too far that is impossible to manage? (company uses minerals, metals, chemicals, etc). Could you provide an example?
Defining context of the organization
Answer:
When determining context of the organization, you need to examine all internal and external issues that can affet your QMS (Quality Managemnet System). When it comes to internal issues, you need to consider products and services, organizational structure, roles, and responsibilities, organizational culture, capabilities, etc. For external issues, the organization needs to consider culture of the markent where it operates, legislations, customer requirements and habits, competitors, etc.
Even for the companies that conduct the same type of business in the same country, the context of the organization can be different because of the various elements of the context that need to be considered.
The clause 8.3.2 j) requires that during design an development planning the organization to consider documented information needed to demonstrate that design and development requirements have been met. This doesn't mean that you need to provide these documented information during the planning phase but to define what documented information must exist at the end of the design and development process to demonstrate that the requirements have been met. For example, in the project plan or project task you will define what documented information will be created as the design and development output, e.g. CAD drawings.