Governance for third-party access

Provider conduct, on record.

Rules agreed in advance with every provider that connects to your systems, a signed account of how each one keeps them, and a record of every time one is broken.

The problem

Your providers come in through doors you opened for them.

An IT supplier on your VPN, a payroll firm on your API, a support company with a remote tool. You vetted them once. When one of them breaks your rules you can block it, and that is all. Nothing was agreed in advance, nothing is recorded, and nothing follows it to the next renewal.

Rows of servers with status lights in a data centre
ProviderDoorRules agreedConduct recorded
IT support supplierVPN✕✕
Payroll providerAPI key✕✕
Software vendorRemote tool✕✕
Outsourced operationsNamed account✕✕

How it works

Both sides check. Rootwall compares and keeps the record.

Nobody hands over logs. Each side checks the agreed rules on its own logs and sends Rootwall a short signed statement.

STEP 1

Agree the rules

Rootwall writes the rules for each provider’s access with you, and the provider accepts them before it connects.

STEP 2

Both sides check

A checker reads your logs where they sit. The provider can run one on its side too. Each sends a signed statement, never the logs.

STEP 3

Compare and record

Rootwall compares the two accounts. Every broken rule is a strike on that provider’s record, ready for your next contract renewal.

Who it’s for

One record, read from both ends of the connection.

A security officer in a dark control room

For the head of security

Your providers answer for their own doors.

Your attention goes back to the doors nobody answers for. The doors you opened for providers come with rules they agreed to and a record you both can see.

Two people shaking hands over a contract

For third-party risk

Evidence for the renewal, not a questionnaire.

A provider’s conduct over the whole contract, rule by rule, with both sides’ signed account. Bring it to the table when the contract comes up.

An engineer with a laptop beside server racks

For providers

Your clients trust you with the keys.

A clean record shows them you deserve it. Send your own signed statements and your account stands beside theirs.

What it is not

It adds a record. It replaces nothing you run.

Not a security operations centre

Your security team keeps its own detection, untouched. Rootwall checks agreed rules and nothing else.

Not a firewall or gateway

Rootwall never sits in your traffic. It sets the rules and keeps the record.

Not identity

Your providers already prove who they are. Rootwall records how they behave once they are in.

The company

Defenders cannot keep watching every door alone. The companies that hold the keys should answer for the doors they use.

Rootwall is a London company built by people from the defending side of security.

Talk to us

Is a provider’s door keeping you up at night?

One line to info@rootwall.ai is enough. No form, nothing to prepare. You will talk to the founder.

Prefer to ask your own AI?

Read https://rootwall.ai/llms-full.txt and tell me what Rootwall is and how it can help me with cybersecurity.