Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

If…, then how…

If our IT is run by a service provider, whose policies apply?

4 decision pointsThe pack behind this answer: Security Policy Management

Add to board memo

The short answer

Recommendation
Your policies govern your information and systems, whoever operates them. Keep ownership and approval of every document on your register with your own people, put the provider's procedures that carry out your standards on that register, and bind the provider to its duties through the service agreement.
Reasoning
Handing over the work does not hand over the accountability. The provider may draft procedures for the systems it runs, but a provider never approves a document that governs its own work. Its procedures that carry out your standards are listed on your register as external documents, with your contract owner as owner. Its purely internal documents are not yours to own or approve, so the contract binds it to a management system to a named standard instead. The service agreement is where the provider's staff are required to acknowledge your policies, give notice of changes to its procedures, and use your exception process.
Considerations
  • The contract duties come from the model text in the CISO Times contract clause library. Your lawyers will adapt it.
  • Large providers often insist on their own terms. Read them against your clauses point by point. Accept the provider's certified standard in place of your schedule only if the certificate's scope covers the service you buy; if you cannot tell, treat it as not covered.
  • Hold firm on the duty not to reduce the security of the service during the term. Without it, the assessment that approved the provider stops describing it.
  • A clause the provider refuses, and which you accept without it, is a gap. Record it as a security exception. If the gap leaves the provider outside appetite or scored Critical, the approver your risk method requires also signs, and the risk goes on your risk register.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 12 steps.
  1. Start

    A service provider runs your IT

    Handing over the work does not hand over the accountability. Your policy framework covers security documents written or operated for you by providers, wherever you require your people or theirs to follow them. It does not cover the provider's own internal documents that you do not require anyone to follow.

    In the pack

  2. Decision

    Which kind of document is it?

    Sort each document into one of three kinds: your own policies and standards; procedures the provider writes to carry out your standards on the systems it runs; and the provider's own internal documents, which govern its business rather than yours.

    In the pack

  3. Step

    Name the policies its staff must follow and acknowledge

    List in the contract the policies the provider must comply with when working on your premises or systems. Require its staff to acknowledge the policies that apply to them, as your own staff do. The provider may be consulted on documents it must follow, but it never approves them.

    In the pack

  4. Step

    Put it on your register, owned by your contract owner

    List each provider procedure that carries out your standards on your register as an external document, with your contract owner as owner and the provider's reference in the notes. Your owner obtains the current version and confirms it is reviewed. Your own approver approves it: a provider never approves a document that governs its own work.

    In the pack

  5. Step

    Leave it off your register; bind the provider by contract

    A provider's internal documents that you do not require anyone to follow are not yours to own or approve. The contract instead requires the provider to run an information security management system to a named standard, such as ISO/IEC 27001 or your own supplier security requirements.

    In the pack

  6. Decision

    Does the contract already bind the provider to these duties?

    Check the service agreement for five things: a management system to a named standard; compliance with your listed policies on your premises or systems; staff acknowledgement of the policies that apply to them; notice of changes to its procedures that affect your standards; and use of your exception process for any deviation.

    In the pack

  7. Step

    Add the missing duties to the agreement

    Use a security requirements clause: a management system to a named standard, compliance with your listed policies, and no reduction in the security of the service during the term. Add the acknowledgement, change-notice and exception duties beside it. A change the provider notifies is a trigger to review the standard it affects.

    In the pack

  8. Decision

    Does the provider insist on its own standards instead?

    This is the usual pushback, and large providers often offer only their own terms. Do not try to rewrite them. Read them against your clauses point by point, and note which points they cover and which they do not.

    In the pack

  9. Decision

    Does its certificate's scope cover the service you buy?

    You can accept the provider's certified standard in place of your own schedule, but only if the certificate's scope covers the service you actually buy. If you cannot tell from the certificate, treat it as not covered.

    In the pack

  10. Step

    Accept its certified standard in place of your schedule

    Hold firm on the clause against reducing security during the term: without it, the assessment that approved the provider stops describing it. The duties about your own systems still apply: acknowledgement of your policies, notice of changes and your exception process.

    In the pack

  11. Outcome

    Record the refused clause as an exception

    A clause the provider refuses, and which you accept without it, is a gap. Record it as a security exception in every case. If the gap leaves the provider outside appetite or scored Critical, the approver your risk method requires also signs the exception, and the risk goes on your risk register.

    In the pack

  12. Outcome

    Your policies govern; the provider's work sits inside them

    Your policies apply to your information and on your systems, whoever operates them. The provider's procedures that carry them out are on your register with an owner of yours. Any deviation by the provider goes through your exception process, never by informal agreement.

    In the pack

Practical checklist

  1. Sort each document: your own policies and standards, provider procedures that carry out your standards, and the provider's internal documents.
  2. List in the contract the policies the provider's staff must follow on your premises or systems, and require them to acknowledge those that apply to them.
  3. Put each provider procedure that carries out your standards on your register as an external document, owned by your contract owner, with the provider's reference in the notes. Have your own approver approve it.
  4. Leave the provider's internal documents off your register, and require in the contract a management system to a named standard.
  5. Check the service agreement for five duties: a management system to a named standard, compliance with your policies, staff acknowledgement, notice of procedure changes, and your exception process.
  6. Add any missing duty. If the provider insists on its own standards, check that its certificate's scope covers the service you buy.
  7. Record any refused clause you accept as an exception, and treat each change the provider notifies as a trigger to review the standard it affects.

Evidence to have ready

  • The service agreement, with the policies the provider must follow and its acknowledgement, change-notice and exception duties.
  • Your register, listing the provider's procedures as external documents with an owner in your organisation and your approval of each.
  • Acknowledgement records for the provider's staff who use your systems.
  • The provider's certificate and its scope, where you accepted its certified standard, and any exception recorded for a refused clause.

Assumptions

  • A service provider runs some or all of your IT under a contract you can change, now or at renewal.
  • Clause content referred to is the model text in the CISO Times contract clause library. Your lawyers will adapt it.

Not covered here