So, the question is how deep should we go into assets that contain other similar assets, and if we should take a building as an asset when we can detail it into smaller parts that could somehow be put together as a whole… I´m probably not explaining myself so well, I hope you will understand as probably this one is a recurring question.
To what extent is up to us to choose the level of detail? How much this will depend on external audit?
Answer:
The quantity of assets and their level of details is totally up to the organization. The external auditor will only verify if your arrangement can provide enough confidence that all relevant risks are being properly assessed and treated.
As tips for handling the asset inventory, you only have to increase the level of details if you identify that by this way you can improve security, or have more efficient operation with acceptable risks. For example, you can have a building as a single asset, but if you identify that a room need extra security in that building, you can have two different assets (i.e., the building and the specific room). On the other hand, if you have similar assets that can share the same control, you can group them in a single asset. For example, laptops, tablets and smartphones can be grouped as an asset name "Mobile devices".
Other examples are network (that can be divided on cabling, switches, firewalls, etc.), and roles in the organization (the different roles can be grouped like users, technical staff, and managers).
Answer:
For OHS objectives this is just the sort of measurable, targeted improvement that is expected for the ISO 45001 standard. The idea is to set a target for improvement, and then make plans to achieve this target and flow these plans down so that everyone knows what they need to do to achieve the target in the planned timeline. You seem to have a good objective for improvement.
For more information on OHS objectives see this article, “How to define ISO 45001 objectives and plans”; https://advisera.com/45001academy/blog/2018/12/04/how-to-define-iso-45001-objectives-and-plans/
Waste audit
Answer:
You don´t need any qualification in ISO 14001 to conduct a waste audit, although it can help you to better understand how to handle waste in an organization. The objective of a waste audit is to determine the types of waste and the locations that will be audited while the aim of ISO 14001 is to manage all the environmental aspects related to an organization, so it covers a broader scope.
There are not specific requirements in ISO 9001:2015 about this issue, however I recommend you to keep track of changes mentioning the review date and the edition number. Regading the edition number without changes, this is totally up to you, I usually don´t change the edition number unless there are some changes in the document. You can develop a procedure stating all these things so everybody in the company can follow and understand the system.
Answer:
Your organization has to answer to those major findings and send your proposals to the auditor. By “off-site” he means that he does not need to go back to your company to accept your answers. Your organization write the answers, send them to him or her, and he or she will accept it or not without going back again to your organization.
Regarding the mandatory documentation related to MOC, you need to retain the following documented information:
- Design and development changes records (clause 8.3.6)
- Production/service provision change control records (clause 8.5.6)
In this tutorial - ISO 27001 standard clauses refers to 4.3.2 and 4.3.3 and in the template the reference document is listed as 7.5. Can you please advise why these are different, and which clauses I should reference, so I can make sure this matches up correctly moving forwards? Can you please advise which one should I rely on?
1. Reference documents
· ISO/IEC 27001 standard, clause 7.5
· ISO 22301 standard, clause 7.5
· BS 25999-2 standard,clauses 3.4.2 and 3.4.3
· Information Security Policy
· Business Continuity Policy
· Policy for handling classified information
· [other documents and regulations specifying document control]
Answer:
First of all, sorry for this inconvenience. Every time you find such discrepancies between the tutorials and documentation, please use the information in the templates, because they are the most updated version.
2 - Also there is mention throughout of ISO/IEC 27001. Can you please confirm what the IEC relates to as I ha ve not come across this before.
Do I keep this referenced within our documentation as the Standard name or should I have this removed? As I work through the video / documentations, I am noticing several discrepancies between the video and the template.
Answer:
The International Electrotechnical Commission (IEC) is an international standards and conformity assessment body for all fields of electrotechnology, and has joined with ISO for the development of ISO 27001, since many controls to protect information are related to electrotechnology. The official name of the standard is ISO/IEC 27001, but you can only refer to the standard as ISO 27001 without problems.
GDPR compliance
Answer:
Let me start by saying that compliance with ISO standards and compliance with a legal requirement are somewhat different. ISO standards are not mandatory and you don't get fined if you do not comply with their provisions nor can they be enforced by governmental bodies. In terms of ISO or any other standard, you get some kind of certificat ion stating you are compliant while for GDPR this is not applicable.
And finally, nor ISO nor any other standard can be used to prove compliance with a legal requirement such as the EU GDPR. What BS:10012 does is give you a framework that you could use in terms of data protection without guaranteeing anything in terms of legal compliance.
Coming back to your original question, I personally think that BS:10012 or ISO 270018 are not required to be compliant with the EU GDPR so unless you need those standards for something else, then you can get certified. ISO 27001 is, however, a good way to prove that you are keeping your information assets including personal data secure which helps in terms of compliance with Article 32 of the EU GDPR.
Personal data that should be protected regardless of which structure within the company or third party processes it. Internally, the whole company is responsible and assigning an owner will only cause confusion and spread the belief that only the owner is accountable for how the personal data is being processed. Ultimately, the company is responsible if the data i s processed in an unlawful manner and not a specific individual/employee.
In terms of your web developer, as he will be acting as your data processor, he is bound by the obligations set up in Article 28 of EU GDPR and you, as a data controller, need to ensure that those obligations are clearly set out in the Data Processing Agreement you need to sign with the processor.