Visit Award Program for cybersecurity awards and recognition.

How to Recognize Third-Party Security Risk Management That Works

Cover Image for How to Recognize Third-Party Security Risk Management That Works
David Matthews
David Matthews

A supplier questionnaire can be complete while an important security question remains unanswered. The organization may still be unclear about who controls administrator access, what happens during a service outage, or whether the evidence reviewed covers the service it actually uses.

Third-party security risk management deserves recognition when someone turns that uncertainty into an informed decision and a dependable working arrangement. The achievement might involve a better purchasing decision, a corrected access arrangement, or a supplier incident plan that both sides can follow.

For an award nomination, show how the work changed the organization's handling of a real dependency. A growing collection of documents is useful only when reviewers can see what those documents helped people decide or improve.

Start with the service and its consequences

Identify the service being reviewed, the business function it supports, and the period covered by the nomination. A supplier may provide several products with different security arrangements. Approval of one should not silently extend to all the others.

Describe the information the service holds, the access it receives, and the consequences if it becomes unavailable or compromised. A service that processes sensitive records raises different questions from one that publishes public material. A small provider with privileged access can warrant more attention than a larger supplier with no access to important systems.

Ask how the team identified those differences and used them to prioritize its work. Where relevant, include dependencies on subcontractors or a common underlying provider. Reviewers do not need an exhaustive supplier map, but they should understand the dependency the nominee made more visible.

Keep the scope practical. A nomination about improving reviews for critical hosted applications should state which applications qualified and which supplier relationships remained outside the project.

Check that evidence answers the right question

A magnifying glass resting on a blank cream folder beside a closed navy folder

A questionnaire, independent report, technical demonstration, and contractual commitment each contribute different evidence. Ask what a document covers, when it was produced, and which parts apply to the service and configuration being considered.

An assurance report covering one environment cannot automatically establish the controls of a separate product. A statement that a supplier supports multifactor authentication does not show that the customer's administrators are required to use it. The review should connect a claim to the relevant service and identify any remaining uncertainty.

Look for proportionate verification. Depending on the question, that might mean reviewing an appropriate report section, confirming a configuration with the service owner, or asking the supplier to explain an exception. Collecting more documents is not always the most useful next step.

The guide to documenting cybersecurity impact can help present this evidence without exposing confidential supplier material. A redacted record should preserve the relationship between the question, the evidence, and the conclusion.

Make shared responsibilities usable

Purchasing a managed service does not settle every operational responsibility. The supplier may operate the platform while the customer controls user accounts, data sharing, and configuration. Reviewers should ask how the team established the division that applies to its arrangement.

Follow one important task. Who approves administrator access? Who removes it? Who receives an incident notification, and who can authorize a response affecting the business? An ownership table becomes meaningful when the named roles recognize their responsibilities and can carry them out.

Evidence might include an approved responsibility record and a service owner's confirmation that the handoff works. If a contract requires notification, explain how that notification reaches someone able to act. Avoid presenting a clause as proof that the operational process has been exercised.

Credit the coordination behind the arrangement. Procurement, security, legal advisers, service owners, and supplier staff may each resolve a different obstacle. The discussion of breaking down silos in security teams helps make those contributions visible.

Follow a finding into a decision

An assessment can identify a weakness without changing the organization's exposure. Ask what happened after a material finding: whether the supplier corrected it, the customer changed its configuration, the organization restricted the planned use, or an accountable owner accepted a defined remaining risk.

Consider a hypothetical application that supports separate administrator accounts but initially grants broad access through a shared account. A review identifies the limitation. Before wider adoption, the service owner establishes named access and the team checks the revised permissions. The useful nomination evidence is the original finding, the agreed action, and the observed result.

If the supplier cannot make a requested change, explain the decision that followed. A temporary exception should have a clear scope, owner, review point, and rationale. Acceptance records establish accountability; they do not show that the weakness disappeared.

Recognition can also belong to someone who made an unsuitable purchase avoidable. Explain the requirement that could not be met and the approved decision, without inventing a financial saving or claiming that an incident was certainly prevented.

Rehearse disruption and the end of the relationship

Two colleagues coordinating by telephone beside a laptop and closed cream folder

Supplier assurance continues after onboarding. A change in service use, access, ownership, or a significant incident may warrant a fresh look. Ask how the team learns about relevant changes and who decides whether the existing assessment still applies.

For an important dependency, trace a disruption scenario. Can the organization reach the supplier through an approved channel? Does each side understand which information to exchange and who makes decisions? If the service is unavailable, what can the business do while it waits?

The guide to tabletop exercises that improve readiness offers a way to assess such rehearsals. Distinguish a discussion of recovery from a technical restoration test, and show which follow-up actions were completed.

Include the end of the relationship where it matters to the claim. Who revokes supplier access, retrieves needed information, and confirms the agreed treatment of retained data? Explain retention constraints and unresolved dependencies. A planned exit is stronger when someone has checked that the required export or handoff is possible.

Measure improvement beyond review volume

Completed assessments describe activity. To assess an achievement, connect that activity to the decisions and safeguards the project was intended to improve.

Useful measures could include the proportion of in-scope critical services with a confirmed owner, material findings with verified actions, or important relationships whose incident contacts were checked. State the population, time period, evidence source, and exclusions for each figure.

Compare similar services and review conditions when claiming progress. A shorter turnaround may reflect a better process, a simpler supplier population, or reduced scrutiny. Explain which changed. Likewise, finding more weaknesses after introducing a better review does not automatically mean the program became less effective.

Pair measures with one traceable example. Reviewers should be able to connect the reported improvement to a real service decision while understanding what the evidence cannot establish.

Build a nomination around accountable change

A compact submission can answer five questions:

  1. Which supplier relationship or service dependency did the nominee improve?
  2. What evidence changed the team's understanding of that dependency?
  3. Which decision or action followed, and how was its result checked?
  4. What remains unresolved, and who owns the next review?
  5. What did the nominee contribute, and how will others maintain the improvement?

Give credit for the difficult work of clarification and follow-through. The person who resolves an ownership gap or makes a supplier finding actionable may create more lasting value than the person who collects the most completed forms. A persuasive nomination lets reviewers follow that contribution from uncertainty to a decision the organization can explain and sustain.