Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
I’m assuming that you do not own the data center.
Considering that, for certification purposes, you need to define at least one physical location which belongs to the organization. This one can be the address of the CEO's home, or some office rented by the organization for administrative purposes(like the company HQ).
Since you are a remote company, you should define your scope in terms of the data you want to protect (i.e., the physical data center should be excluded, but the data hosted in this data center should be included) and exclude all remote sites.
These articles will provide you with further explanation of ISMS scope definition:
This tool can also help you:
There are no specific direct requirements regarding the process and/or equipment qualifications. There is a requirement in the ISO 13485:2016 6.3 Infrastructure states that the organization will document requirements for the maintenance activities, control of the work environment, and monitoring and measurement.
Further on, in requirement 7.5.6 Validation of processes for production and service provision is stated that the manufacturer must validate any process where the resulting output is not apparent. In this requirement is stated which elements must be covered for the validation.
ISO 27001 is not mandatory to implement TISAX, but since they share many similar requirements, you can adopt ISO 27001 to make TISAX implementation and audit easier.
For further information, see:
No, medical devices are not subject to the falsified medicines directive. Implementing the UDI number and registration of the devices in the EUDAMED is a way to prevent falsified medical devices.
1. What documents will I need to write in order to be compliant with GDPR?You can find the list of documents required by GDPR in this article:
2. Is it for example possible to write that we are often changing providers and that the client should contact us to get the correct information?
I wouldn’t recommend this approach. As a web hosting company, you should act as a data processor for your customers. Thus, in the Data Processing Agreement, according to Article 28 GDPR - Processor, you must mention what sub-processors you use and what they do exactly with your customers’ personal data. According to Article 13 GDPR - Information to be provided where personal data are collected from the data subject, your customers, acting as data controllers, must inform data subjects about the processors they are using. Since there would be only one web hosting company – yours – it wouldn’t make sense to mention a category.
Please also consult these links:
If as a calibration laboratory you want to add more methods to the calibration certificate you supply to a client, that is not an issue, as long as you are accredited for them. You need to report the method used, which could be a standard method, in-house or modified.
I’m assuming that by DORA you mean the Digital Operational Resilience Act
Considering that, DORA’s purpose is to strengthen the financial sector’s resilience to ICT-related incidents, and although not mandatory for DORA, ISO 27001 can provide a robust baseline to support compliance with this objective.
Regarding personal certifications, you can consider:
These articles will provide you with a further explanation of ISO 27001 personnel certifications:
For courses related to these certifications, please see:
Please note that the application of controls in SoA is not necessarily related to the ISMS scope, but to the results of risks assessment and identified applicable legal requirements (e.g., laws, regulations, and contracts). This means that some controls will be implemented by your company, and some controls by your suppliers or partners.
For example, even if you do not include outsourced IT services in our ISMS scope, you may have a contract with a customer requiring the implementation of technical control, then this technical control needs to be stated in the SoA as applicable and implemented by your supplier.
1- How to do a gap analysis of the status of my management system against compliance with the ISMS requirements ISO 27001:2013
To perform a gap analysis of your ISMS against ISO 27001, please access our free tool: https://advisera.com/27001academy/free-iso-27001-gap-analysis-tool/
This is a simple question-and-answer list that allows you to visualize which specific elements of an ISMS you’ve already implemented, and what you still need to do.
2- List of documents required to comply with ISMS ISO 27001.
Included in your toolkit you have a list of documents that shows you which are the mandatory documents to be compliant with ISO 27001.
3. How to develop an ISMS ISO 27001 communications program to interested parties, what should this program contain?
Please note that ISO 27001:2013 requires you to define a communication process, although there is no requirement that a communication program needs to be developed or documented.
Considering that, communication is an activity that is performed by many processes in information security according to ISO 27001, with different purposes and interested parties. So, having a centralized communication program would overhead people responsible for communication with activities that may not be a part of their attributions. That’s the reason there isn’t a specific template for a communication program.
The main documents in the toolkit that define how communication needs to be done (which could be considered as part of a communication program) are:
4. How to develop an ISMS ISO 27001 awareness program for stakeholders, what should this program contain?
For information security these are some security practices you should consider (without more information about your context is not possible to suggest additional alternatives):
These articles will provide you with further explanation about security practices:
You can use the Training and Awareness Plan template, located in folder 9 Training and awareness, to document the activities to be performed.
5. How to develop a Management review procedure program
Please note that ISO 27001 does not require a procedure for Management Review to be documented, so to be compliant with the standard you can just use the Management Review minutes template located in folder 11 Management review.
In case your doubt is about review periodicity, the minimum is to perform a management review once a year, or more often if any major change happens that can influence information security (e.g., there is a new client who has very particular requests regarding the confidentiality or availability of your systems). However, it could be done more often (e.g., quarterly) if the management wants to be more involved in operational issues.
For further information, see:
No matter whether the production process is outsourced, that process must be in the scope. From the market point of view, regardless of the fact that production is outsourced, that company is responsible for the product.