Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
Patch management and vulnerability management would be best covered in A.12.1 - Security Procedures for IT Department, located on folder 08 Annex A Security Controls >> A.12 Operations Security since it involves change management.
This article will provide you a further explanation:
Você pode definir o escopo em termos de apenas uma parte da organização (ou seja, o Banco de Dados), mas em geral, para pequenas e médias empresas, a melhor abordagem é incluir toda a organização no escopo do SGSI, porque o esforço para separar o escopo para tais organizações pode não valer a pena.
Estes artigos fornecerão uma explicação adicional sobre a definição do escopo:
Esses materiais também irão ajudá-lo com relação à definição do escopo:
Once you have identified the disruptive scenarios you have to handle, broadly speaking, the development of a continuity plan based on ISO 22301: 2012 requires the development of:
These materials will provide you a further explanation about developing a continuity plan:
To see how a Business Continuity Plan compliant with ISO 22301 looks like, I suggest you see the free demo of our Business Continuity Plan at this link: https://advisera.com/27001academy/documentation/business-continuity-plan/
Thank you, Rhand!
The ISMS scope states the information you want your ISMS to protect, so what you want to protect (in your example data and application software) needs to be stated in the ISMS. The detail that it is located in a cloud solution can be kept to be stated during the Risk Assessment.
This article will provide you a further explanation about the scope definition in the cloud:
1 - My situation is that I am an intern at a small company whose servers are in the cloud (***), and they have a website of their own. So my question is implementing ISO27001 would be meaningless for such architecture, if not how should i define the context of the organization in such a case.
SO 27001 aims the protection of information regardless of where it is, so it is also applicable when the information to be protected is hosted in a cloud solution.
The definition of the ISMS scope when information is on a cloud solution will depend on the control you have over the cloud
This article will provide you a further explanation about defining a scope considering cloud models:
2 - Also what sources would help a beginner like me to achieve this implementation of the standard. By the way, I started the course online in advisera titled "ISO 27001:2013 Lead Implementer Course" is it a good start?
To help beginners to implement ISO 27001 Advisera provides several articles and downloadable materials the can provide guidance.
Additionally, I suggest you take a look at the free demo of our ISO 27001 Documentation Toolkit at this link: https://advisera.com/27001academy/iso-27001-documentation-toolkit/
This toolkit has the mandatory and most commonly used documents for an ISO 27001 implementation, and they include comments that can help to customize the documents to your organization's needs.
Regarding the Lead Implementer course, it is a good way to start an understanding of how to implement ISO 27001.
These articles will provide you a further explanation about ISO 27001:
These materials will also help you regarding ISO 27001:
Yes, core tools are extremely important in IATF 16949:2016 application. Especially in the new product launch process, production and quality processes, APQP, PPAP, FMEA, SPC, MSA must be applied for IATF 16949:2016 requirements.
The necessity of these applications is specified in IATF 16949: 2016 standard clauses 8.1,8.3,8.5,8.6,8.7,9.1.1.1 and customer-specific requirements. Especially according to OEM customer-specific requirements, while giving PPAP for a new project, there must be evidence of core tools in the PPAP file. At the same time, the IATF standard is a technical standard and an important purpose is the reduction of scrap, waste, and ensuring continuous improvement. Achieving this goal cannot be achieved without applying Core tools.
For more information please see the following:
Yes, you can. I always recommend following that practice, particularly, when an internal auditor has less experience, or has little time to prepare an audit to the whole management system. For example, in this free webinar on demand - How to perform an ISO 9001:2015 internal audit - https://advisera.com/9001academy/webinar/how-to-perform-an-iso-9001-2015-internal-audit-free-webinar-on-demand/ - I give an example of preparing a partial audit.
You can find more information below
Design and implementing a quality management system (QMS) implies being knowledgeable about ISO 9001:2015. Now the standard is less and less bureaucratic, it is up to each organization the task to design, develop and implement its QMS.
Setup a project sponsor, a project manager and a project team. Determine the scope of the QMS, your organization may decide to include only certain lines of business. Ensure top management support, get training and as a first step perform a Gap analysis, to determine the amount of work to be done - comparing what your organization already has in place versus ISO 9001:2015 requirements. From that GAP Analysis you can develop your Project Plan, listing what needs to be done, by whom, until when.
Then, an important step is to design a model of how your organization work as a set of interrelated processes. For example:
Decide how to describe and monitor those processes.
From there it is implementation in order to close the gaps found. Then, perform an internal audit and the management review. There you can decide if your organization is ready for a certification audit.
This is a very short description of the journey but below you can find more detailed information:
A - Let me use new company to represent a new company with an established business model, like a restaurant, like a new shoe manufacturing plant, or a new transport company.
B - Let me use start-up company as a designation for a project of company in search of a business model. 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.
So, for situation B it is too early to certify. For situation A, I think it is easier to get ISO certification than with an established company (with same resources and motivation). An established company has to unlearn some practices and that it is not always easy.
You can find more information below: