Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
First is important to note that ISO 27001 does not prescribe how to document interested parties, so documenting them by name or by category are acceptable approaches.
But please note that, to fulfill clause 7.4 - Communication, you need to determine with whom to communicate, and depending on the information to be communicated, maybe it will be necessary to identify clients individually in certain circumstances.
This article will provide you a further explanation about interested parties:
These materials will also help you regarding interested parties:
I'm assuming you are referring only to controls from section A.17.1
Considering that, controls from ISO 27001 Annex A section A.17 (Information security aspects of business continuity management) aims to minimize risks that, in case of an event that disrupts business operations, the information will be kept protected, and operations that rely on them will be resumed as quickly as possible.
To show compliance with controls of this section an organization needs to:
This article will provide you a further explanation about business continuity for ISO 27001:
These materials will also help you regarding business continuity for ISO 27001:
1. How can ISO 27001 ensure data integrity in a company that needs to create all its security policies from scratch
ISO 27001 Annex A has controls that can be applied to minimize risks that information is changed or destroyed without authorization (e.g., A.9.1.1 Access control policy, and A.12.1.2 Change management), and that changes performed can be tracked and undone if needed (e.g., A.12.4.1 Event logging, and A.12.3.1 Information backup), thus helping protect information integrity.
For further information, see:
This material will also help you regarding ISO 27001 controls:
2. is the return on investment of an ISO 27001 project feasible?
ISO 27001 was designed to help organizations apply controls based on relevant requirements and in levels related to their risk tolerance.
Considering that, provided that the ISO 27001 project is aligned to the business' and interested parties' (e.g., customers, regulation bodies, suppliers, etc.) needs and objectives, its return on investment is feasible.
This article will provide you a further explanation about ISO 27001 implementation:
To develop a security culture you must consider these points:
For further information, see:
This material will also help you regarding awareness and training:
You are going to audit the Management Representative. An audit is about collecting evidence from the contrast between reality and audit criteria. You should start by collecting the audit criteria. Which documents, in your QMS, mention the Management Representative and its authorities and responsibilities? Then, read that documentation and look for situations that you think you want to check, that you want to confirm. For example, you may read that the Management Representative is responsible for conducting quarterly performance reviews about processes and action plans. You can ask to see evidence that the performance review took place, what its decisions were, and if it has a positive impact on the organizations’ performance. For example, you may read that the Management Representative is responsible for ensuring that corrective actions are implemented, effective, and closed. You can ask to see evidence that shows if corrective actions are defined, implemented, evaluated as effective, and closed.
You can find more information below:
You can change ISMS policies anytime you identify the need to, but you need to evaluate who will be impacted by the changes, and what the impacts will be, to decide who needs to be informed, and what is the information to be communicated. For example:
A “generic” email address is an email address that does not incorporate personal information (i.e. info@company.com or marketing@company.com ) while a “personal” email address refers to a specific individual (i.e. name.surname@company.com, or n.surname@company.com, or surname@company.com, etc).
Germany and the UK are both ruled by the European Union General Data Protection Regulation 2016/679 which has direct application across all EU.
In the UK the GDPR will be enforceable until the 31st December 2020 when the Brexit transition period will end and of course, it will continue even after for companies subjected to its application (companies processing personal data of individuals living in the EU). However, UK privacy law has many principles in common with GDPR which has been taken as a model for data protection law across the world.
You can find more information about GDPR and email marketing here:
Unfortunately, I can not answer about CMMI. However, I can answer about ISO 9001. Startups, in reality, are not yet companies, they are still projects of companies in search of a successful business model and customer fit. So, a startup is like an experiment being done. The startup can be called a company only after finding the right business model, a customer fit, and when it starts scaling. Only then, the procedures and internal standards are ready to be documented.
You can find more information below:
Check all the promises your organization makes in its quality policy and try to translate each one into a measurable challenge, a quality objective.
You can find more information below: