Colour theme
Book a consultation

Reviewing supplier security risks

Review suppliers by the data, access and business functions they handle. Check security evidence, incident contacts and recovery arrangements.

A person reviewing printed documents beside a calculator

An accounting firm, software supplier or IT provider may hold information or access your business depends on. A problem in that relationship can affect your work even when your own systems are operating normally.

Review suppliers according to what they handle and what would happen if the service stopped. The Canadian Cyber Centre’s small-business supply-chain guidance recommends an inventory and attention to suppliers that support critical functions. Start there, with the business owner who uses each service.

Record the dependency and access

For each important supplier, record the service, contract owner, support contact, renewal date and information shared. Include remote access, administrator permissions and integrations into other systems.

Ask what work would stop during an outage and whether another supplier uses the same underlying platform. Two contracts can still depend on one hosting or identity service.

Prioritize relationships with sensitive information, broad access or a business-critical function. Keep a reason for the priority so a change in access or service can trigger a new review.

Ask for evidence that fits the service

Ask how the supplier encrypts your data, how its staff get and lose access, whether its systems are independently tested, how it handles incidents and how it restores the service. Request evidence relevant to the product you’re buying and the information it will hold.

If the supplier offers an assurance report or certification, check its scope, period and exclusions. Note any responsibilities it assigns to customers. A report about a different service or an old assessment may not answer your question.

For a supplier with remote access, confirm named accounts, authentication, who agrees to each connection and what gets logged. Ask IT to restrict the connection to the work required and test how it can be disabled during an incident. Your own controls still matter when a supplier is compromised.

Establish information-handling terms

Document what the supplier may use the information for, who else processes it, retention and deletion arrangements, and the locations involved. Discuss unresolved questions before sending the data.

The OPC’s outsourcing guidance explains that organizations subject to PIPEDA need to account for privacy when outsourcing. Review applicable provincial and sector requirements as well. A contract doesn’t remove your responsibility for the information or settle every legal requirement.

Have someone with legal and business authority review terms that affect customer records, liability or incident notification. Avoid copying a standard notification period into every agreement without checking the service and obligations involved.

Practise the incident handoff

Agree who the supplier will contact, how you’ll verify the message and what information you’ll need to decide your next steps. Include service status, affected systems or records, containment actions and follow-up updates.

Use a tabletop scenario: the supplier reports compromised support access during a busy workday. Who can disable the connection? Who assesses your records and customers? How does the team keep working while access is restricted? Record unanswered questions and assign follow-up.

Plan for interruption and exit

Check whether the supplier’s recovery arrangements meet your needs and whether you have a usable workaround. A second supplier is helpful only if the transition, data and responsibilities have been prepared.

For a cloud service, test data portability before renewal. Keep open risks, accepted exceptions and review dates in the supplier record. Talk to us if you need help mapping third-party access and checking your most important dependencies.


Featured Image Credit