[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract
[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract

THIRD PARTY RISK MANAGEMENT

Third Party Risk Management and Software Security

Castler proves that your critical vendors' software can be rebuilt and run without the vendor. Every verified release gets a signed Proof of Recovery, so your third-party software security evidence stays current.

100+ enterprise customers17 regulatory mandates covered across 9 jurisdictionsISO 27001, SOC 2 Type II, CERT-In and PCI DSS assured
Recoverability Audit · on Castler
6/6 sealed

Core banking

Core banking vendor

SCANNING

Payment switch

Payments vendor

SCANNING

Risk and fraud

Risk technology vendor

SCANNING

KYC

Identity vendor

SCANNING

Lending origination

Lending platform vendor

SCANNING

Treasury and reconciliation

Treasury vendor

SCANNING

What Is Third Party Risk Management?

Third party risk management covers every stage of a vendor relationship: selection, contract, monitoring, incident response and exit. It answers one question: what happens to the business if a vendor fails, is acquired, drops support or is attacked?

Regulators now expect third party risk management to include tested exit and recovery plans, not only vendor questionnaires. The effort matters most for critical vendors, because a failure there stops operations. For software, third party risk management has one extra requirement: the institution must be able to run the software without the vendor.

Selection

Contract

Monitoring

Incident response

Exit

What Is Third-Party Software Security?

Third-party software security means checking that vendor software is complete, buildable, safe and recoverable. Third-party software security evidence must be tied to the exact release running in production. Castler produces this evidence for critical vendors on every verified release.

A full check includes:

A software bill of materials (SBOM) that lists every component inside the application.

Vulnerability severity and licence exposure for those components.

A cryptographic inventory (CBOM) of the stack.

Checks for hidden dependencies, such as private vendor repositories or a vendor-hosted licence server.

Who Are Critical Vendors?

Critical vendors supply software that your core operations cannot run without. A vendor is critical when its failure would stop a regulated service, break a customer commitment or trigger a regulatory report. Regulators use terms such as critical or important functions and material service providers for the same idea.

Vendor size does not remove the risk. Large critical vendors still get acquired, discontinue products, ship faulty updates or suffer attacks. In a bank or NBFC, critical vendors typically supply:

Core banking

Payment switch

Risk and fraud

KYC

Lending origination

Treasury and reconciliation

How Do Critical Vendors Fail?

Castler's incident tracker lists five causes, each with a real case:

Insolvency

Synapse (2024) left $265M frozen and affected 10M+ users.

Acquisition

After Broadcom bought VMware (2023), AT&T was quoted a renewal increase of 1,050%.

Discontinuation

Nirvanix (2013) gave customers such as National Geographic and Fox two weeks to move petabytes of data.

Faulty update

CrowdStrike (2024) affected 7,000 Delta Air Lines flights and cost about $500M.

Cyberattack

Jaguar Land Rover (2025) halted 5,000 suppliers, cost £1.9B and caused a five-week shutdown.

Each case is a third party risk management event. In each one, the software from critical vendors stopped and losses grew until recovery.

How Does Castler Handle Third Party Risk Management for Critical Vendors?

Castler handles third party risk management for critical vendors in four steps:

Step 1, Custody:

The vendor deposits source code, build scripts, runtime configuration and documentation into Castler's secure cloud custody. Every release is captured and versioned.

Step 2, Agentic verification:

AI agents rebuild, deploy and replicate the application in a clean environment. No vendor involvement and no documentation are required.

Step 3, Engineer's Seal:

A named Castler engineer reviews the evidence and signs it.

Step 4, Signed Proof of Recovery:

You receive a numbered, signed pack for that exact release.

Verification takes 6 to 18 hours per codebase, compared with 2 to 4 weeks. Cost is about 90% lower than the current verification cost. When a vendor ships a new release, a new cycle produces a new Proof of Recovery, so third-party software security evidence follows the software in production.

6–18 hrs

Castler verification

2–4 wks

Traditional human-led verification

Third Party Risk Management Regulations for Critical Vendors

Castler maps its evidence to 17 mandates across 9 jurisdictions. In India:

Globally:

Across all of them, third party risk management and third-party software security for critical vendors now need current, testable evidence.

Third Party Risk Management Cost

Cloud Storage

$2,000

per application per year

Secure custody and a deposit report.

Standard Verification

$3,500

per application per year

Adds build verification, SBOM and CBOM for third-party software security.

Premium Recoverability

$7,500

per application per year

Adds independent rebuild, deployment, run and a signed Proof of Recovery.

Bundles for up to 10 applications: $7,500, $15,000 and $45,000 respectively.

There is no setup fee. Start with one of your critical vendors and expand across the estate.

Book a 15-min Demo

FAQ

Frequently Asked Questions

What is third party risk management?+

Third party risk management is the process of identifying, assessing and controlling the risks that come from vendors. For software, it includes proving that critical vendors' software can be recovered if the vendor fails.

What is third-party software security?+

Third-party software security is the work of making sure vendor software is complete, safe, current and recoverable. It covers the SBOM, vulnerabilities, licences, cryptography and a tested rebuild.

Who are critical vendors?+

Critical vendors are the vendors whose software your core operations cannot run without. Examples include core banking, payment switch, risk and fraud, KYC, lending and treasury software.

How do I test whether critical vendors' software can be recovered?+

Rebuild and run the software in a clean environment without the vendor. Castler does this with AI agents, and a named engineer signs the evidence as a Proof of Recovery.

How long does it take to verify a critical vendor's software?+

Castler verification takes 6 to 18 hours per codebase. Traditional human-led verification takes 2 to 4 weeks.

Does third party risk management need software escrow?+

An escrow agreement covers custody of the code. Regulators also expect evidence that the code can be recovered, so Castler adds a signed Proof of Recovery on top of custody.

Does Castler cover third-party software security?+

Yes. Each Proof of Recovery includes an SBOM, a build report and a replication report. Standard Verification also adds a CBOM, with vulnerability severity and licence details. Together they give you third-party software security evidence for each release.

Which critical vendors should I verify first?+

Start with the vendors whose failure would stop a regulated service, such as core banking, payment switch, risk and fraud, KYC, lending and treasury.

Can Castler cover all of our critical vendors?+

Yes. You can begin with one critical application and expand verification across the whole software estate as vendors and releases are added.

THIRD PARTY RISK MANAGEMENT

Find out how many of your critical vendors are recoverable

Book a 15-min Demo. We will map your critical vendors, name the regulation that applies to you and show you a real signed Proof of Recovery.

Book a 15-min Demo
ISO 27001SOC 2 Type IIPCI DSS

No spam · Reply within one business day