Legacy contracts inevitably fall behind changing regulation, but rewriting agreements is not always the answer. A senior third-party cybersecurity risk executive argues that firms should identify where obligations truly sit, prioritize genuine gaps and combine contracts with continuous monitoring, internal controls and formal risk acceptance.
Financial institutions should stop
treating contract remediation as the automatic answer to every new third-party
regulatory requirement.
Legacy agreements inevitably fall
behind changing rules, but effective risk management requires firms to
determine whether a contractual gap represents a genuine vendor obligation, an
internal control weakness or a risk that can be addressed through monitoring
and governance before embarking on costly remediation programs.
Speaking at CeFPro’s latest Vendor
and Third Party Risk Europe event, the Head of Information and Cybersecurity
Third Party Risk at a leading European regional bank argued that contracts are
only one component of a much broader control environment.
Institutions should combine
contractual protections with continuous monitoring, internal governance and
effective risk assessment rather than assuming every regulatory change demands
another amendment.
Legacy contracts are particularly
vulnerable because they reflect requirements in force when they were signed.
As regulation develops, clauses
become outdated and gaps emerge. However, the risk executive said organizations
can become more predictive by involving compliance, finance, cybersecurity,
threat intelligence and other specialist functions in determining what
agreements may need to accommodate during their lifecycle.
That starts before a contract is
signed. Regulatory expectations should be considered during the
request-for-proposal stage, making potential vendors aware that requirements
may change during the relationship.
Contracts can also provide rights to
conduct additional assessments or audits when regulatory developments require
them.
The executive argued that
well-designed clauses can anticipate change by establishing upfront that
vendors may have to adapt when relevant regulatory requirements emerge.
This does not eliminate negotiation,
particularly with strategic suppliers, but it reduces the need to reopen
agreements whenever authorities introduce new expectations.
Regulation itself should not be
viewed simply as an obstacle. “The intention of them is not to block or slow
down your business,” he said.
Instead, requirements are designed to
increase awareness and encourage organizations to develop processes, standards
and contractual protections that reduce risk.
No contract, system or cybersecurity
investment can eliminate risk entirely.
Where gaps do emerge, prioritization
becomes critical. Firms first need an accurate inventory identifying services,
contracts and providers from their most critical relationships downward.
Regulatory developments can then be
mapped against that inventory to identify which agreements genuinely require
attention.
Assessment should follow, potentially
through continuous monitoring, periodic reviews or regulatory-triggered
assessments.
The resulting gap must then be
classified correctly. It may sit within the contract, but it could instead be a
process, technology or internal governance issue.
That distinction matters because
financial institutions can mistakenly attempt to pass their own regulatory
obligations directly to suppliers.
A vendor may legitimately reject a
contractual demand because the underlying rule applies to the regulated
financial institution rather than the service provider.
“You need to translate your
regulatory requirements into something that is driven by the contract as an
obligation from the vendor, remembering that not every obligation is applicable
to your vendor,” the executive said.