Having in mind that first one is mandatory and the second one is not, how does it sound to merge them together? I find it much more comfortable and logical to have these procedures together, if there is a clear distinction in the document regarding facilities and systems/ equipment / networks and so on. Is this a valid approach?
Answer:
First it is important to note that controls from ISO 27001 Annex A are mandatory only if at least one of these situations happen:
- There are unacceptable risks that justify the application of the control
- There are legal requirements (e.g., laws or contract clauses) to which the organization must comply with that demands the application of the control
- There is a top management decision to implement the control, by considering it as good practice.
If no one of the above conditions happen, there is no need to implement a document related to that control.
Considering that, you can merge these two controls in a single document if this makes easier for your organization to understand and implement them.
My question for you is, can I modify the security control objectives from Annex A (ISO/IEC 27001) and rewrite them so that they represent my company's security policy?
For example, take information security objective A.7.1.2, which states: "To ensure that employees and contractors are aware of and fulfill their information security responsibilities." Can I reword this to say (something like): "It is our company's policy to ensure that employees and contractors are aware of and fulfill their information security responsibilities."?
Answer:
First it is important to note that a policy sets general directions, while an objective is specific about what must be achieved. Considering that, you can use elements from security control objectives from Annex A to fulfill your needs regarding wr iting policy statements, but you must consider the different purposes they have to build the text.
Your example is too specific to be used as a policy statement (e.g., what a about customers or suppliers which access your information? How do you handle them?). A proper example would be: "It is our company's policy that personnel which handles information must be prepared to protect them properly." In this example you do not limit to whom this statement applies to (it is valid also for customers, suppliers, and other entities), and how you are going to accomplish that (e.g., by means not only of awareness, but also by education, training, etc.).
The question is : in a small digital agency (up to 20 employees, including management), which documentation and policies / procedures are required and which ones are an overkill for such a small organization like my company?
Answer:
First it is important to note that some documents and records are mandatory to fulfill clauses from the main sections of the standard (sections 4 to 10), and these are:
- Scope of the ISMS (clause 4.3)
- Information security policy and objectives (clauses 5.2 and 6.2)
- Risk assessment and risk treatment methodology (clause 6.1.2)
- Statement of Applicability (clause 6.1.3 d)
- Risk treatment plan (clauses 6.1.3 e and 6.2)
- Risk assessment report (clause 8.2)
- Records of training, skills, experience and qualifications (clause 7.2)
- Monitoring and measurement results (clause 9.1)
- Internal audit program (clause 9.2)
- Results of internal audits (clause 9.2)
- Results of the management review (clause 9.3)
- Results of corrective actions (clause 10.1)
Another situation is that some documents are required to fulfill controls that are mandatory if at least one of these situations happen:
- There are unacceptable risks that justify the application of the control
- There are legal requirements (e.g., laws or contract clauses) to which the organization must comply with that demands the application of the control
- There is a top management decision to implement the control, by considering it as good practice.
If none of the above conditions happen, there is no need to implement a document related to that control. Examples of such documents are:
- Inventory of assets (to implement control A.8.1.1)
- Acceptable use of assets (to implement control A.8.1.3)
Considering that, besides the documents to fulfill clauses from the main sections, without a detailed evaluation of an organization, it is not possible to define how many documents an organization would have, and which ones would be an overkill.
Examples: Would you say contracts are a primary asset or a supporting asset. How about job descriptions, NDA, SLA, DPA, Sales offers. Is there a good technique on how to categorize properly? In the risk assessment table template from Advisera, only suggested assets are listed.
Answer:
ISO 27001 does not prescribe asset categorization, so you do not need to implement further categorization than that is already provided on the suggested list of assets on the risk assessment table template (add such categorization will only unnecessarily complicate the process.).
Contract, job descriptions, NDA, SLA, and DPA are documentation, while sales offers is information (unless this refers to the name of a document)
Answer:
I worked with more than a dozen construction companies in implementing and certifying a quality management system according to ISO 9001.
ISO 9001 is very helpful for organizations that work with projects and organizations that have no repetitive product or service year after year.
You can decide how to organize your management review, either through routinely scheduled meetings or through a more continuous review process.
The minimun required inputs ISO9001 that top management needs to review are the following:
- Results of Audits.
- Customer Feedback
- Process Performance and product conformity
- Status of Preventive & Corrective Actions.
- Follow-up Actions from previous Management Reviews.
- Changes that could affect the Quality Management System.
- Recommendations for Improvement
When creating a quality policy you need to consider the following:
- is appropriate to the purpose and context of the organization
- supports the strategic direction of the organization
- provides a framework for the quality objectives of the organization
- includes a commitment for the fullfilment of applicable requirements (customer requirements, regulatory requirements and ISO requirements)
- contains a commitment for continual improvement
Regarding quality objectives - they are goals that can be measured and that are releva nt for the organization in order to increase customer satisfaction. They also must be consistent with the quality policy.
You will also must determine how and when quality objectives will be achieved, what resources will be needed, who will be responsible, and how the results will be assesed.
Yes, ISO 20000 certification for internet data center is good idea.
Here are few benefits of the ISO 20000 implementation (and certification):
- proof of excellence in IT Service Management (ITSM)
- getting ITSM “under control” – meaning managed, measured and improved processes, clear roles&responsibilities, etc.
- distinctiveness from other, non ISO 20000 certified, companies
- integration of ITSM and business operation as well as stakeholders (and their expectations)
- “same language” inside organization
You can find out more in the article “5 key benefits of ISO 20000 implementation” https://advisera.com/20000academy/blog/2016/02/09/5-key-benefits-of-iso-20000-implementation/
Planning communication
Answer:
Your organization, with ISO 9001:2015 clause 4.2, determined relevant interested parties and their relevant requirements and/or expectations. So, considering those relevant interested parties, your organization should determine what needs to be communicated to each party in terms of the quality management system. For example, your organization may want to communicate process performance to employees, or health care results to clients or their families or the local community. For each “what to communicate” your organization should plan (I use a table):
when to communicate – once per month? once per year? Every quarter?
to whom communicate – clearly state who will be the recipients of communication
how will you communicate? – a newsletter? An internal meeting? An e-mail? A press release? An internal report?
Who will communicate? – Which function or functions will be responsible for the communication?
I am a ISO lead auditor with 14 yrs experience in the standards and am looking also at expanding my portfolio to include IT ISO auditing
Any ideas or help appreciated.”
Answer:
Based on your experience description, I would start by contacting consultancy organizations in the market to offer my services as a freelance consultant. At the same time, I would start my commercial activity in order to find clients on my own, and I would develop my marketing activities by starting a blog, or any other way of showing my know-how and experience. About entering IT ISO auditing I can say that it is a very hot job right now with strong demand worldwide:
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.
If you decline, your information won't be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.