The ISO 14001 environmental policy outlines the overall intentions and direction of how the company will relate to its effect on the environment. This statement needs to come from top management, since it is a primary directive for how every individual in the company will perform their job in relation to environmental impact. This is where you display what commitments your company will make to controlling and improving the environmental impact that you make.
In order to be compliant with the standard, the policy must be appropriate to the context of the organization, to provide framework for setting the environmental objectives, include commitment to protect the environment, fulfill legal and other requirements and continual improvement.
Requirements for Quality Manual can be found in clause 7.5.1.1. In order to be compliant with IATF 16949, the manual must include the following:
- scope of QMS (Quality Management System) and justification for exclusions,
- documented procedures or reference to them,
- organization's processes and interaction between them
- a document or matrix that shows where within the QMS the customer-specific requirements have been met.
Documented process vs procedure and product safety
Answer:
Documented process is just another way to require documented procedure. It only allows you to document the process in any way you find the most suitable and that is through flowchart, quality plan or any other way, but the essence is the same.
Clause 4.4.1.2 titled Product Safety requires a documented process (procedure) for the management of product safety. This clause defines 13 normative elements that must be included in the documented product safety process. These 13 requirements include identification of product safety characteristics, inclusion of safety characteristics with approvals in design and process FMEA’s, control of safety characteristics at the point of manufacturer with documentation in control plans with specific reaction plans, and defined responsibilities for product safety management including the definition of an escalation process and flow of information, inc luding top management, and customer notification. Additionally, those personnel involved in product safety related processes will have specific training.
Audit observation
(Hello Dejan, I have a doubt, in recent audit we were made the observation that we have to document a data encryption policy, which is described according to the type of information, status (in transit, storage, moving) and according to their type of storage (servers, computer equipment, etc.), if they require the applications of cryptographic controls, and reviewing the document of the policy of the use of cryptographic controls nothing comes of it, thanks for your support.)
Answer: By the description you gave to us, the informatio n required by the audit can be found in the template "Information Classification policy", which is referenced in the "Policy on the Use of Cryptographic Controls" (on section 3.1). Both documents are part of the ES ISO 27001 Documentation Toolkit you bought. You can find these templates in the following folders:
- Information Classification policy : folder 08 Annex A, sub-folder A.8 Asset management
- Policy on the Use of Cryptographic Controls : 08 Annex A, sub-folder A.10 Cryptography
In the Information Classification policy template, the information about type of information, status and type of storage can be found in the table on section 3.4 - Handling classified information. E.g.: "the document must be stored in encrypted form", and "when files are exchanged..., they must be encrypted"
Thunderstroke?!?
Yes, a thunderstroke is only another way by which a lightning is know.
Including business process description and scoping in the ISO project
Answer: Together with the toolkits you bought you also have access to a video tutorial that can help you fill the Statement of Applicability. The procedure is the same for considering the specific controls of ISO 27017 and ISO 27018.
You can find these tutorials in Conformio, it the menu "Repository", in folder "Video tutorials" - see what you need to click here: https://www.screencast.com/t/T5rLxMgc3UJz - these tutorials are quite useful because they will show you how to fill out the real data in the documents, what elements of the documents are mandatory and which are not, etc.
Certification requirements
(What do I need so that my company can be ISO certified?)
Answer: For earning an ISO management system certification, your organization must define, implement, operate, control and improve a management system that is compliant with the requirements of the desired standard, and go through a certification process under an accredited certification body.
Answer: I'm assuming you are referring to ISO management systems. Considering that, since 2012, all ISO management systems are being developed according the same structure:
1- Scope
2 - Normative references
3 -Terms and definitions
4 - Context of the organization
5 - Leadership
6 - Planning
7 - Support
8 - Operation
9 - Performance evaluation
10 - Improvement
This makes easier to integrate them, because in clauses 4, 5, 7, 9, and 10, the texts of the standards are almost the same, and the specifics of each standard are concentrated on clauses 6 and 8.
Answer: To identify if a control is needed for the scope of an organization you need:
- to perform a risk assessment to identify if there are unacceptable risks related to the scope that can be mitigated by the control you are considering;
- to evaluate if legal requirements, such as laws, industry regulations, or contracts, demands the application of the control.
- to consult top management decisions regarding which controls should be applied regardless the results of risk assessments and legal requirements.
If after that you identify no reason to apply the control you can consider it out of your ISMS scope.
2 - How to use ISO 27000 series on small/medium small companies, where the it function is 1-10 people!?
Answer: ISO 27001 was designed to be implemented by organizations of any size, but small companies need to take care they do not write too many documents (the standard itself only require few of them).