How to monitor supplier security risks after onboarding
A supplier may meet your security requirements when you first assess them. But that doesn’t mean their security posture will stay the same throughout your relationship. They may introduce new subcontractors, change how they store your data, experience a security incident, or leave vulnerabilities unresolved.
If you only assess suppliers before onboarding, you can miss changes that affect your organization’s information and services. You need an ongoing process to identify these changes, understand their impact, and follow up on emerging risks.
ISO 27036 addresses information security throughout supplier and acquirer relationships. Its principles support establishing security expectations and maintaining appropriate oversight as the relationship develops. This guide explains how to put that into practice through ongoing supplier security monitoring.
Why should you continue supplier security monitoring after onboarding
An initial third-party security assessment gives you a view of a supplier’s security controls at a particular point in time. It helps you decide whether the supplier can meet your requirements before you establish or expand the relationship.
However, several changes can affect that decision later:
- Changes to security controls: A supplier may change its access controls, encryption practices, vulnerability management processes, or security policies.
- New subcontractors: A supplier may begin relying on another provider that handles your information or supports an important service.
- Security incidents: A breach or other incident may expose weaknesses in the supplier’s systems or response processes.
- Unresolved vulnerabilities: Security findings may remain open beyond agreed remediation deadlines.
- Changes to services or data access: A supplier may begin processing additional information, connecting to more systems, or providing services that carry greater risk.
These changes can affect the level of risk a supplier presents. Ongoing monitoring helps you identify them and decide whether existing security requirements and safeguards remain appropriate.
6 ways to monitor supplier security risks after onboarding
You don’t need to monitor every supplier in the same way. Focus on the supplier’s access to your information, the importance of its services, and the potential impact of a security issue.
1. Review supplier security information regularly
Ask suppliers to provide updates on security controls that are relevant to your relationship. This may include changes to policies, certifications, audit findings, vulnerability management, and access control practices.
For example, if a supplier’s ISO 27001 certification is part of your assurance requirements, check its validity and scope during periodic reviews. If the supplier changes the systems or locations covered by its certification, determine whether the change affects the services it provides to you.
You can establish a review schedule based on supplier risk. Higher-risk suppliers may need more frequent reviews, while lower-risk suppliers may require less intensive oversight.
What to monitor:
- Changes to relevant security policies and procedures.
- Certification status, scope, and renewal.
- New audit findings and corrective actions.
- Changes to security controls affecting your services.
- Updates to the supplier’s security responsibilities or contacts.
2. Track vulnerabilities and remediation progress
A supplier may identify security weaknesses through vulnerability scans, penetration tests, internal audits, or other security reviews. The important part is understanding whether those findings could affect your organization and whether the supplier is addressing them.
Agree on how the supplier will communicate relevant findings and progress on vulnerability remediation. You can then track open issues against agreed deadlines and request updates when actions are delayed.
Suppose a supplier identifies a vulnerability in an application that processes your customer information. You should understand whether the affected application is part of your service, what exposure exists, and when the supplier expects to resolve the issue.
What to monitor:
- Significant vulnerabilities affecting relevant systems or services.
- Remediation status and overdue actions.
- Repeated security findings.
- Exceptions to agreed patching or remediation timelines.
- Evidence that corrective actions have been completed.
3. Monitor supplier security incidents and changes
A supplier’s security incident may affect your organization even if your own systems are not directly compromised. You need to know how the supplier will notify you, what information it will provide, and what actions both parties must take.
Agree on incident notification and communication arrangements before an incident occurs. These should identify the appropriate contacts, the information the supplier must share, and how the parties will coordinate their response.
Also monitor changes that may affect the security of the relationship, such as new data processing arrangements, changes in hosting locations, or modifications to system access.
What to monitor:
- Security incidents affecting your information or services.
- Changes to incident response contacts and procedures.
- Relevant changes to data storage or processing locations.
- Changes to system integrations and access arrangements.
- Corrective actions following an incident.
4. Review subcontractor and fourth-party changes
Your supplier may depend on subcontractors, cloud providers, or other external service providers. Changes in these relationships can introduce risks that are not immediately visible to your organization.
Establish which subcontractor changes the supplier must notify you about. Pay particular attention to providers that can access your information, process sensitive data, or support critical services.
For example, if your supplier moves part of its data processing to a new cloud provider, you may need to review the provider’s security arrangements, the data location, and any changes to the responsibilities agreed between the parties.
What to monitor:
- New or replaced subcontractors.
- Changes to subcontractor services or access to your information.
- Security incidents involving relevant subcontractors.
- Changes to subcontractor assurance or certification status.
- Whether the supplier continues to meet its agreed security obligations.
5. Reassess suppliers when significant changes occur
Scheduled reviews help you maintain visibility, but some changes require attention before the next review date.
A security incident, major vulnerability, new service, or significant change in data access may affect the supplier’s risk level. In these situations, carry out a targeted reassessment rather than waiting for the next scheduled review.
For example, if a supplier begins processing a new category of sensitive information, review whether its existing access controls, data protection measures, and contractual security requirements cover the expanded service.
Common reassessment triggers include:
- A significant security incident.
- A major change to the supplier’s services or technology.
- New access to sensitive information or critical systems.
- A change in subcontractors or service delivery locations.
- Serious or overdue security findings.
- Expired or withdrawn assurance evidence.
6. Follow up on risks and corrective actions
Identifying a supplier security risk is only useful if someone follows up on it. Maintain a record of findings, agreed actions, responsible parties, and target completion dates.
Not every finding requires the same response. You may ask a supplier to resolve a control gap, provide additional evidence, introduce compensating safeguards, or explain why a particular issue does not affect your services.
For risks that remain unresolved, determine whether you can accept them, need additional controls, or should reconsider the supplier relationship.
Supplier security monitoring process should cover:
- The identified security issue and its potential impact.
- The supplier and internal owners responsible for addressing it.
- Agreed remediation steps and deadlines.
- Progress updates and supporting evidence.
- The final risk decision and approval.
This gives you a record of how supplier security issues were handled and whether the agreed requirements continue to be met.
How ISO 27036 supports ongoing supplier security monitoring
ISO/IEC 27036-2:2022 provides requirements for information security in supplier and acquirer relationships. It covers how parties establish, implement, operate, monitor, review, maintain, and improve those relationships.
This makes it relevant beyond the initial supplier assessment. You can use its relationship-focused approach to establish how security requirements will be maintained and verified after onboarding.
For example, your supplier arrangements can define:
- Which security changes the supplier must communicate.
- How and when the supplier provides evidence of agreed controls.
- How both parties handle security incidents and relevant events.
- Who is responsible for reviewing findings and following up on corrective actions.
- How security requirements are reviewed when the services or relationship change.
The specific monitoring activities and review schedules should reflect your supplier arrangements and risk exposure. ISO/IEC 27036-2 provides the requirements framework; it does not prescribe one universal monitoring schedule or checklist for every supplier.
For a step-by-step approach to applying the standard, see our guide: how to implement ISO 27036 in your supplier security program.
Manage ongoing supplier risks with CyberArrow
Tracking supplier security risks becomes harder when assessments, evidence, findings, and remediation updates sit in separate documents and spreadsheets.
CyberArrow helps you organize third-party risk management through centralized vendor risk assessments, continuous monitoring of vendor compliance, and remediation collaboration with vendors. You can document supplier findings, monitor identified risks, and follow remediation actions in one platform.
Schedule a free demo to see how CyberArrow can help you maintain visibility into supplier security risks.
FAQs
What is ongoing supplier security monitoring?
Ongoing supplier security monitoring is the process of reviewing a supplier’s security posture after onboarding. It involves tracking relevant security changes, incidents, vulnerabilities, subcontractor arrangements, and remediation activities to determine whether the supplier continues to meet agreed security requirements.
How often should you monitor supplier security risks?
Monitoring frequency should reflect the supplier’s risk level and the importance of its services. Higher-risk suppliers may need more frequent reviews, while lower-risk suppliers may require less intensive oversight. Significant incidents or changes should trigger an additional review regardless of the regular schedule.
What is the difference between a third-party security assessment and ongoing supplier monitoring?
A third-party security assessment evaluates a supplier’s security controls at a particular point in time, often before onboarding. Ongoing supplier monitoring continues after onboarding by tracking changes, reviewing new evidence, following up on security findings, and reassessing risks when significant events occur.