DPO requirement for online company who has 1 employee
Answer:
Appointing a DPO is only compulsory if (a) the processing is carried out by a public authority or body, except for courts acting in their judicial capacity; or (b) the core activities of the legal entity consist of processing operations which, by their nature, their scope and/or their purposes, require regular and systematic monitoring of data subjects on a large scale; or (c) the core activities of the legal entity of processing on a large scale of special categories of data pursuant to Article 9 of the EU GDPR and personal data relating to criminal convictions and offences referred to in Article 10 of the EU GDPR.
So, as you can see there is no need for you to be appointed DPO.
Answer:
The Quality Manual is a document that tops the QMS documentation hierarchy. So, organizations normally make the Quality Manual a document to be approved by top management, the source of authority in the organization. BTW, I would not use the word process here.
The following material will provide you information about documentation structure:
Answer: When you perform the risk assessment, you should also assess the risks related to these ISMS documents - if the risks are high, then you should allow only a very few people to access them; if the risks are low, then you can allow a wider circle of people to access them.
Answer: For a smaller company of up to 50 employees the best is to include your whole company into the ISO 27001 scope, because it would be too costly to try to keep a part of such small company out of the scope.
For larger companies (e.g. more than 500 employees) you should choose a department or a location to include in the scope for the beginning - after you successfully implement the standard in such smaller scope, then you can expand further.
For companies between 50 and 500 employees - you should assess which approach between the two described better fits you.
Answer:
I list all equipment and determine which is critical and deserves/needs preventive maintenance. Those that are not critical I only record any curative maintenance done and costs incurred. ISO 9001:2015 is very general about infrastructure, what is important is its effectiveness. You don’t want nonconformities or delays, for example, because of equipment breakdown or equipment malfunction.
The following material will provide you information about maintenance:
2. Requirements for Quality Manual at a minimum (without copying the AS9100 standard with wording changes to fit the organization.
Answer:
1. For the required documents I would recommend reading our free whitepaper on the documents required for AS9100: https://info.advisera.com/9100academy/free-download/as9100-rev-d-list-of-mandatory-documents
2. As for the quality manual this is no longer a strict requirement of AS9100 Rev D. However, in clause 4.4.2 the standard does mention a list of documented information that can be collected into a single source document and called a quality manual. This includes: description of relevant interested parties, scope of the QMS, description of organization processes and their application, the sequence of processes and the assignment of responsibilities and authorities for processes.
For some further help w ith implementation check out our project checklist: https://info.advisera.com/9100academy/free-download/project-checklist-for-as9100-rev-d-implementation
Multi controllers
Answer:
“Controllers in common” or “independent controllers” are both processing personal data but independently and for different purposes and there is no requirement to have a document stating their obligations as they are both bound by the controller obligations under GDPR. The GDPR only requires to have such document between controllers and processors or between joint controllers.
This is the reason for which we don`t have such a document in the toolkit. Please no te that the Supplier Data Processing Agreement is not suited to be used in a controller to controller situation.
Incident management procedure - treatment of minor events (3.3)
Answer:
ISO 27001 is not specific on how to record the incidents, which means you can do it in any way that you see fit. This means you could log minor incidents that happen the first time in the Incident log, but in such case I would recommend that you mark separately first-time incidents from those that are happening repeatedly.
SoA - A.6.1.3 - Incident Response Plan
Answer:
Incident response plan is a document needed only if you want to become compliant with ISO 22301, it is not needed for ISO 27001. Therefore, it is not part of ISO 27001 Toolkit (it is a part of ISO 27001 & ISO 22301 Premium Toolkit).
To become compliant with ISO 27001 control A.6.1.3 (Contact with authorities) it is enough to specify in your Statement of Applicability who in your company will be in contact with e.g. police, regulatory agencies, etc. - the standard does not require you to have an extra document for that purpose.
Are Annex A.11 controls mandatory?
Answer:
ISO 27001 says that none of the controls are mandatory, and that you have to apply a control only if there is a reason to do so. The reasons could be risk assessment, contractual or regulatory requirement, or e.g. business decision from your management.
So physical and environmental controls are not mandatory, and you should apply them only if the risks are too high, if you have some client asking you to do this, or if there is some other business reason to do so.
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.
If you decline, your information won't be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.