Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
1. As I fill out the risk assessment table and do the risk assessment, we are finding that some risk should be owned by a third party connected to our ISO scope, is it ok to list them as the asset and risk owner, they would be responsible if the risk would surface.
Risks related to elements outside the ISMS scope should be treated by controls of section A.15 - Supplier relationships. Through Service Level Agreements (SLAs), Operational Level Agreements (OLAs) or Terms and Conditions of Service, the organization makes clear and enforces the expected information security controls to be applied. In this scenario, someone in the organization still is the risk owner, but the treatment is delegated to the third party.
For further information, see:
2. We have some SDLC (systems development life cycle) controls listed in 06 SOA, we stated in our scope document that software development is not in scope, however, if we know that controls are in place already should we document that in the SOA?
The main purposes of the SoA are to identify which controls are applicable or not in the ISMS scope, the justifications for such decisions, and the implementation status of those controls deemed as applicable, but you can document implemented controls that are not part of the ISMS scope in the SoA as a good practice (ISO 27001 requirements do not prohibit this).
This way you will have a centralized information source about all implemented controls you have, even if they are not implemented in the ISMS scope. This can be useful, for example, if in the future you need to include such controls in the ISMS scope (you will have quick information about what you already have).
You only need to pay attention to ensure that the situation of the control as not part of the ISMS scope is perfectly clear in the justification. For example:
"Program source code is not in the ISMS scope, however, this control is tracked in the SoA as a good practice, to keep a centralized database of the organization's applied controls."
This article will provide you a further explanation about SoA:
Please note that this template is an appendix, developed to define how all the necessary resources for a critical activity will be recovered. The potential disruptive incident scenarios are documented in its main document, the Business Continuity Strategy, section 3.2 - Risk management (this is one of the documents you already have)
To see how the description of a disruptive incident looks like, I suggest you take a look at the free demo of our Examples of Disruptive Incident Scenarios at this link: https://advisera.com/27001academy/documentation/examples-of-disruptive-incident-scenarios/
The main rules here are:
With clear control objectives, you will know which resources you need, where to apply them, who needs to be involved, and when adjustments are needed, avoiding low performance and waste. However, this is only half of the way.
With clear links between control objectives and business objectives, you can easily demonstrate to top management that the information security effort is paying off.
With clear responsibilities people will know what is expected from them, focusing on activities that add value to the business, and avoiding unrelated activities.
Finally, with proper competencies, the personnel will be more engaged with information security (they will know why is important to do what they have to do and how to perform such tasks)
These articles will provide you a further explanation about security objectives:
First, the word is certification not accreditation. Organizations are certified according to ISO 9001 by certification bodies. Certification bodies are accredited by accreditation bodies according to ISO/IEC 17021-1.
So, after implementing a quality management system (QMS) an organization may decide to get certified. There are several certification bodies available. Organizations select three or four and send a request for quotation and select the one that best suits the requirements. Please check these two articles:
After reaching an agreement and signing a three year contract, your organization and the certification body set a date for an audit, a certification audit. Please check these articles:
After the certification audit an audit report is issued and if an organization has nonconformities it has to treat them. After getting the certification, the organization will have yearly surveillance audits to verify compliance and improvement of the QMS. Please check this article:
Please check more information about ISO 9001 below:
ISO 27001 and GDPR give no unique solution on how to dispose of your printed documents. ISO 27001 requires classifying documentation and you can implement different procedures depending on the information incorporated in the printed document. Is there any confidential information? Are you dealing with a particular kind of personal data under Article 9 GDPR? Do the printed documents contain no personal information or anonymized information? The solution can be different.
Any disposal should comply with your data retention policy and data protection policy in order to avoid accidental destruction of documentation which is considered a data breach because of its impact on the integrity of data.If you decide to appoint an outside company, you need to check their compliance with GDPR requirements and other quality standards such as ISO 27001 and the recycling process. Under GDPR you should make a data processing agreement with your supplier because the outside company will process (through destruction) data on your behalf.
Here you can find some useful information on printed documentation under ISO 27001
Our template of Supplier Data Processing Agreement may be of help:https://advisera.com/eugdpracademy/documentation/supplier-data-processing-agreement/
You can also consider enrolling in this free online training EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
If you need more information, you can also consider enrolling in this free online training ISO 27001 Foundations Course: https://advisera.com/training/iso-27001-foundations-course/
To understand the acceptance values of the process capability, the first thing to look at is customer-specific requirements. Apart from this, according to AIAG PPAP revision, 4 manual published by Ford, GM, DaimlerChrysler on 1st of June 2016, the acceptance criteria were determined as follows.
For more information please to read the following article:
Possible threats to this scenario related to employees are:
This article will provide you a further explanation about security in projects:
Article 12 GDPR contains most of the data subject request flow. It requires that data controller to:
The responsibility for complying with data subject rights is on the data controller and note that fines for noncompliance are the highest (up to 20 million Euro or 4% annual turnover if higher). Therefore, you must ensure that your staff is trained in complying with data subject rights.
You should set rules in your internal procedures on data subject rights. Here you can find some useful templates:
GDPR Consent & Data Subject Rights Toolkit: https://advisera.com/eugdpracademy/eu-gdpr-consent-data-subject-rights-toolkit/
Here you can find the free EU GDPR Data Subject Access Request Flowchart: https://info.advisera.com/eugdpracademy/free-download/eu-gdpr-data-subject-access-request-flowchart
Here is the text of the Article 12 from GDPR: https://advisera.com/eugdpracademy/gdpr/transparent-information-communication-and-modalities-for-the-exercise-of-the-rights-of-the-data-subject/
You can also consider enrolling in this free online training EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
The ISMS scope can cover all organization, or only specific locations, processes, or information.
The main point when considering this approach is the effort required to keep the ISMS scope separated from the rest of the organization's elements (for small and mid-sized organizations many times the effort is not worthy, and it is better to include all the organization in the ISMS scope)
These articles will provide you a further explanation about the scope definition:
1. How can the Organization be compliant with these Controls?
A.6.1.3: Contact with Authorities: Does it mean contact with the Superior Authority who is also the supreme body for GDPR?
In case your organization has to answer to this authority, then this is one way to fulfill this control. Other examples are law enforcement agencies and emergency services.
2. A.6.1.4: Contact with Special Interest Groups: Does having ISACA Memberships of some other Interest Groups are taken into consideration?
In case these groups can help you support your ISMS you can consider them to fulfill this control.
This article will provide you a further explanation about interested groups: