Colour theme
Book a consultation

Putting supplier security controls into practice

Turn supplier security reviews into working controls. Set up access, verify software sources and practise disabling a supplier connection safely.

Two colleagues talking across a table with stacked binders and a water carafe.

A supplier has passed your security review and the contract is signed. Someone still needs to set up its access, check the work it performs and remove permissions when the job ends.

Use your supplier risk review to choose the relationships that need attention first. This guide covers the next step: making the agreed controls work in your systems.

Give each connection an owner

Record the supplier’s business contact, the person approving its work and the IT person responsible for access. Include support portals, remote management tools, integrations and accounts held by subcontractors.

For each connection, write down what it can reach and why. An accounting integration that reads invoices has different requirements from a support tool that can run commands across staff computers.

The Cyber Centre’s supply-chain guidance recommends categorizing suppliers by business importance and setting security requirements in contracts. Use those decisions to define the access you’ll allow and the evidence you’ll review.

Set up and test the access

Use named accounts for people where the service supports them. Require MFA, limit permissions to the work agreed and put an end date or review date on access. Avoid giving a supplier your own administrator credentials.

Have IT test both sides of the boundary: the supplier can do the agreed task, and it can’t reach an unrelated system or record. A separate network segment needs enforced traffic rules. Giving it a name doesn’t isolate anything.

For an application connection, inspect the permissions it has and the identity it uses. A non-human integration needs controls suited to its credentials and permissions. It won’t use an employee’s MFA prompt for every automated action. The SaaS integration guide covers that separate review.

Control software and support changes

Obtain software, updates and hardware through verified supplier or manufacturer channels. Confirm support requests through a contact route you already hold before installing a new remote-access tool.

For a significant supplier change, record the affected systems, approval, test results and recovery route. Choose the test and deployment schedule according to exposure and business impact. An urgent security update shouldn’t wait for the next routine supplier meeting.

Check what logs your services provide and who reviews them. Useful events can include new accounts, changed permissions and remote-support sessions. Agree the review and alert responsibilities with your IT provider; don’t assume a product subscription includes someone responding to its alerts.

Practise restricting a connection

Use a planned test or tabletop exercise with the supplier. Ask what you’d do if its support account were compromised during business hours.

Confirm who can disable the account, revoke application access or block the remote connection. Check the effect on business work before testing any disruptive action. Account disablement may leave existing sessions, tokens or separate credentials that need additional action.

Keep a manual workaround for critical work and a verified incident contact. Your vendor breach checklist can help organize the information you’ll request during a real incident.

Close the relationship properly

When the work ends, remove the agreed accounts, permissions, credentials and support tools. Verify each change in the system that grants access. Arrange the return or deletion of records under the contract and applicable privacy requirements, including any retained backups.

Keep unresolved exceptions with an owner and review date. Our Cybersecurity service can help check third-party access and turn a supplier review into a practical implementation plan.


Featured Image Credit