Nomenclature recommended for control of the documentation
As you know, establish a common codification for all documents is not mandatory in the standard, but for me is recommendable because your system will be better ordered. There are various ways, one can be: ISMS-TypeDocument-NameDocument-Version. Example: ISMS-Policy-SecurityPolicy-v1, ISMS-Procedure-InternalAudit-v1, ISMS-Report-InternalAudit-v1, etc.
And always you have to generate evidences, in this case for the approval of the Top Management you can use a record of a meeting.
Secure System Engineering Principles Document
It is in another document. Keep in mind that, as you know, it is related to the control A.14.2.5, and it is below the section "A.14.2 Security in development and support processes", so to comply with this point you can use this template Secure Development Policy - you will find it in the toolkit in folder 08 Annex A - A.14 System acquisition, development and maintenance: https://advisera.com/27001academy/documentation/secure-development-policy/
Some questions about ISO 27001:2013
The purpose is to define a person or entity with the accountability and authority to manage a risk (this a definition that you can find in the ISO 27000:2014). And to determine the risk owners you should aim for someone who is closely related to processes and operations where the risks have been identified. Please read this article for more information Risk owners vs. Asset owners in ISO 27001:2013: https://advisera.com/27001academy/knowledgebase/risk-owners-vs-asset-owners-in-iso-270012013/
Is a communication plan mandatory in the ISMS documentation ? (clause 7.4)
The objectives mentioned in clause 6.2, does it refer to the objectives in the Statement Of Applicability (e.g. : in my company, we chose the whole Annex A for our SoA)
Answer:
The objectives in ISO 27001 clause 6.2 can be set both for the whole ISMS, and/or for the control objectives in the Statement of Applicability - usually, the objectives are set at two levels: (1) the general ISMS level, and (2) at the level of security processes or security controls. See also this article: ISO 27001 control objectives Why are they important? https://advisera.com/27001academy/blog/2012/04/10/iso-27001-control-objectives-why-are-they-important/
After the Risk Assessment you need to perform the Risk Treatment, and basically for each risk you have 4 options: a.- Apply security controls, b.- Transfer the risk to another party, c.- Avoid the risk by stopping an activity that is too risky, d.- Accept the risk (when the cost for mitigating the risk is higher that the damage itself). In accordance with the situation that you are described, the bes t option for your business is d. In this case, I recommend you to talk with Top Management, because they have to know this situation and they need to accept formally the risks.
The important here is that you have to define roles and responsibilities of employees of the Organization that are involved in the scope of the ISMS (furthermore, as you know, business strategy and objectives, capabilities and resources, etc).
In our templates, each policy and procedure defines roles and responsibilities, this is so because the ISO 27001 does not require you to have a centralized list of security roles and responsibilities. You can read more information about this here: https://community.advisera.com/topic/roles-and-responsibilities-2/
Third Party SLA for out-of-scope Systems
Sorry for the delay! Here you have our answers:
Each company should include in its ISMS scope only the assets they control directly so overlapping of assets means that they didn't set the scope correctly; and sharing the asset list is not necessary if the ISMS scope document is written precisely enough. The certificate of the ISO 27001 is only for 1 organization, so your organization is responsible of the maintenance of his certificate (in terms of his scope). At this point I recommend you to read this article "How to define the ISMS scope: https://advisera.com/27001academy/knowledgebase/how-to-define-the-isms-scope/
It is necessary to study each situation, but generally in accordance with my last point, each auditor has to audit each ISMS (based on the scope of each one). So, in this scenario you can develop this SLA, but anyway there will be 2 different ISMS, with 2 different scope, and 2 different internal audit + 2 different certification audit.
Please, if you need more information, give us more information about your situation (scope of your organization, scope of your customer, etc).
Risk Assessment Toolkit
Our Risk Assessment toolkit identifies assets owner, so if you have applications (you can consider it as type of asset), you can have owners to those applications. Also our Risk Assessment toolkit identifies vulnerabilities and threats (and risk owners). Basically there are no questions in our documentation, but catalogs of assets, threats and vulnerabilities the asset owners can choose from. You can download our template Risk Assessment and Risk Treatment Methodology at this URL (you can see a free version if you click on Free Demo tab) : https://advisera.com/27001academy/documentation/Risk-Assessment-and-Risk-Treatment-Methodology/
Implementation Checklist
The first thing is that you need all necessary documents (you can use all our templates). Second thing is to adapt all documentation to your organization and implement them. An example: You have our template for the Methodology Risk Assessment (to calculate risks), but what assets, vulnerabilities and threats do you have in your organization? So, you need to complete each document with the information of your business, and generate evidences.