Digital Risk Protection: Scope, Program and Providers
Skip to content

Digital Risk Protection

Digital risk protection (DRP) is the practice of watching the parts of the internet an organization does not control for threats aimed at it: impersonation of its brand and people, its credentials and data in criminal sources, its code and secrets in public repositories, and weaknesses in what it and its suppliers expose.

On this page

Each confirmed finding is then carried through to a response, such as a password reset, a key rotation, a fix or a takedown. The term names a scope of work more than a single tool, and providers draw its edges in different places.

This guide covers what the category includes, how it differs from threat intelligence and attack surface management, how a program runs and is measured, and what to ask a provider.

Why the Category Exists

Much of the preparation for an attack now happens on infrastructure the target never sees. A criminal registers a domain, copies a login page, buys a search ad or a batch of stolen passwords, and only then contacts a victim. Security tools inside the network have nothing to inspect until that contact arrives, which is the gap that digital brand protection and its neighbors cover.

The FBI described one version of this in a December 2022 public service announcement. Criminals bought search engine ads that impersonated real brands, and the ads led to copies of the official sites that delivered malware or collected login and financial details. The FBI advised businesses to use domain protection services that alert them when similar domains are registered.

Credentials and data follow the same pattern. A staff password stolen from a home laptop can be found and used without any alert inside the organization.

  • Outside the perimeter: The domains, accounts and repositories involved belong to someone else, so internal logs say nothing until they are used.
  • Before the attack: Registration, cloning and trading usually come before the first phishing email or sign-in attempt, which leaves time to block, reset or remove.
  • Across teams: A single campaign can touch security, finance, legal, communications and customer support, so the program needs owners outside the security team.

Brand and Impersonation

The brand area looks for anyone using the organization’s name, look or people to deceive customers, staff or suppliers. That covers lookalike domains and cloned sites, fake mobile apps, fake company and executive profiles, fake recruiters, and ads that bid on the brand name.

Findings here usually end in a block and a takedown request, and they often need communications and legal staff as well as security. Our guide to brand and executive impersonation follows the people side across social media, email and ads.

Dark Web and Credential Exposure

This area watches criminal sources for the organization’s accounts, data and access: forums and markets, Telegram channels, ransomware leak sites and stealer logs. A credential finding is a lead to check, since a leaked password may be old, reused from another service or taken from a device infected last week, and only the identity provider’s records say which.

Data or access offered for sale also goes to the incident response team, because it can mean an intrusion is already under way. Our guide to stealer logs explains what infected-device records contain and how a match is worked.

Code and Secret Leaks

Public code is the least visible part of the scope. Staff, contractors and vendors push repositories that carry keys, configuration files, internal hostnames and sometimes real customer data, and Git keeps every version in its history.

The closing action is rotation by the owner of the secret, followed by a log search for use and a cleanup of the repository. Our guide to secrets in public code repositories covers history, forks, validation and cleanup in detail.

Third Parties and Suppliers

Suppliers hold an organization’s data, run its software and sometimes publish its code. Their exposure becomes the organization’s exposure, and most of it is visible only from outside.

The NIST Cybersecurity Framework 2.0 sets this expectation. GV.SC-07 asks that the risks posed by suppliers and other third parties are understood, recorded, prioritized, assessed, responded to and monitored over the course of the relationship. DE.CM-06 asks that external service provider activities and services are monitored to find potentially adverse events.

  • Supplier code: A vendor’s public repository that holds the customer’s production passwords, keys or hostnames.
  • Supplier breaches: Customer data posted on a leak site after a breach at a service provider, which the provider may report late or not at all.
  • Supplier impersonation: A lookalike of a supplier’s domain used to send false invoices or bank detail changes to the organization’s finance team.
  • Supplier exposure: Internet-facing systems at a managed service provider that connect into the organization.

A program adds key suppliers to its scope by name. Our page on cyber risk management covers supplier risk as part of the wider risk register.

How the Disciplines Compare

Digital risk protection, threat intelligence and attack surface management share data sources and are often sold together. They answer different questions, and the difference decides who owns each finding.

NIST defines threat intelligence as threat information that has been aggregated, transformed, analyzed, interpreted or enriched to provide context for decision making. Threat intelligence is about attackers in general, digital risk protection is about one organization’s name, people, data and code, and attack surface management is about the organization’s own internet-facing assets.

Digital risk protection Threat intelligence Attack surface management
Main question Is anyone outside using our brand, credentials, data or code against us? Who is attacking organizations like ours, and how? What do we expose to the internet, and what is weak about it?
Subject The organization’s identity and assets as they appear on others’ platforms. Threat actors, campaigns, malware and infrastructure. Domains, hosts, services and certificates the organization owns.
Typical finding A cloned login page, a leaked staff password, a key in a public repository. A report on a phishing kit, a list of indicators, a new exploit. An exposed admin console, an expired certificate, a dangling DNS record.
Closing action Takedown, reset and session revocation, key rotation. Detection rules, blocks and hunts updated. Fix, decommission or accept the exposure.
Main consumers Security, legal, communications, finance, customer support. SOC, detection engineering, threat hunters. IT operations, cloud and network teams.

In practice the disciplines feed each other. Intelligence about a phishing kit tells a DRP team which page code to match, and an asset inventory tells it which domains are in scope.

The external attack surface is where the overlap is largest. Digital risk protection borrows the exposures that only show from outside, such as a remote access gateway open to the internet, a hostname left pointing at a deleted cloud resource, or an owned domain with no DMARC policy, and joins them to its other findings. A leaked VPN password matters more when the gateway it opens is also exposed, and our guide to external attack surface management explains discovery source by source.

How a Program Runs

A digital risk protection program runs as a loop that repeats daily for some sources and continuously for others. Each stage has an output that the next stage needs.

  1. Scope. The organization lists what to protect: domains, brand and product names, logos, official social accounts, executives, code organizations on GitHub and GitLab, key suppliers and internet-facing ranges.
  2. Collect. Monitoring runs across the sources for each area: domain registrations and certificate logs, web content, app stores, social platforms, search ads, code platforms, paste sites, forums, Telegram, leak sites and stealer logs.
  3. Confirm. An analyst or an automated check decides whether a hit is real, relevant and current, and dismisses resellers, fan pages, old breaches and passwords that have since changed.
  4. Score. Each confirmed finding is ranked, so a live page collecting passwords is worked before a parked domain or a password that has since changed.
  5. Respond. The finding goes to the team that can act: identity for credentials, developers for keys, legal or a takedown provider for impersonation, IT for exposed systems.
  6. Verify and watch. The program checks that the reset held, the key no longer works and the site is offline, then keeps watching for the same content to return elsewhere.

Confirmation is where programs differ most. A raw feed of keyword matches can bury a team, so the useful output is a short list of findings that someone has already checked, with the evidence attached.

Owners for Each Finding

A program crosses team lines, so each kind of finding needs a team that decides and a team that acts. Writing this down before the first live case avoids a debate at the moment speed matters.

Finding area Decides Acts Kept informed
Lookalike domains and cloned sites Security lead Security operations, with legal for disputes Communications and customer support
Fake apps and social accounts Brand or digital owner Security operations, through the platform’s report route Customer support and fraud
Executive impersonation Security lead, with the executive’s office Security operations The executive, finance and HR
Staff credentials and stealer logs Identity owner Identity and security operations The affected user and their manager
Customer credentials Product or fraud owner Customer operations Customer support
Keys and secrets in public code Owner of the system the key opens Developers and cloud administrators Privacy officer when personal data is involved
Supplier exposure Supplier relationship owner The supplier, with internal access owners Procurement and legal
Exposed systems and DNS System owner IT operations Security lead

Some rules keep the table workable. Any team in the Acts column can block a domain or disable an account at once, while takedown requests and customer messages wait for the owner in the Decides column. Every row also names a deputy, since live phishing pages and working passwords rarely appear during office hours.

Response By Finding Type

Each finding type has its own first action, and the order matters. A leaked password gets a reset and a session revocation together, so neither the password nor a stolen token keeps working, and a key is rotated before anyone spends time scrubbing history.

Finding First action Follow-up Closes when
Leaked staff password Check whether it still works and whether the account has MFA. Search sign-in logs for use from unfamiliar locations, then reset the password and revoke sessions. The old password fails and no unexplained sign-ins remain.
Stealer log entry Reset passwords from a clean device and revoke sessions for every account in the log. Review sign-ins from the infection date and deal with the infected device. The device is clean and the accounts are secured.
Key or token in public code Ask the owner to rotate it. Search cloud and application logs for its use during the exposure. The old key fails and the log search is complete.
Cloned site or lookalike domain Capture evidence and block the domain on mail and web filters. Search mail logs for messages from it, then request removal. The site is offline and recipients are warned.
Fake app or social account Capture evidence and warn customers through official channels. Report it to the store or platform under its impersonation policy. The listing or account is removed.
Exposed system or dangling DNS Hand it to the system owner with the evidence. Fix, remove the record or take the system offline. A retest shows it closed.

Takedown requests rely on the duties of registrars, hosts and platforms. ICANN’s Registrar Accreditation Agreement requires accredited registrars to keep an abuse contact and to take reasonable and prompt steps to investigate and respond appropriately to reports of abuse.

Some governments run takedowns for their own brands. The UK NCSC’s Takedown Service works with hosting providers to remove malicious sites that impersonate UK Government brands and adds them to safe browsing lists that browsers use to block access.

When an investigation shows a device was infected, the work moves from monitoring to incident response, which our guide to infostealer response covers step by step.

A Week in a Running Program

Single findings are followed from start to finish in the guides linked above. A program’s own work is deciding which of many findings are real and getting each to its owner, which one week at Acme Corp shows.

  1. Monday, a parked domain. Monitoring flags acmecrp.com, a new registration with no mail records and no page. It matches none of Acme’s partners or resellers, scores low as a typosquatting candidate and goes on watch.
  2. Tuesday, an old breach. A credential list on a forum holds 40 acmecorp.com addresses. The identity owner finds that 37 belong to leavers or predate a password change, and the other three are reset with sessions revoked after the sign-in logs show no use.
  3. Wednesday, a key in a supplier’s repository. A code search finds Acme hostnames and a storage key in an old commit on a vendor’s public account. The key opens Acme’s own cloud account, so Acme’s administrator rotates it within the hour, and the audit log shows no calls from unknown addresses.
  4. Thursday, the domain goes live. The Monday domain gains mail records and a copy of Acme’s customer sign-in page. Security operations block it, the security lead approves a removal request, and communications posts the real sign-in address.
  5. Friday, a fake support account. A customer forwards a reply from an account using Acme’s logo. Its link leads to Thursday’s page, so the two findings become one case and the account is reported to the platform.
  6. Friday, the review. The weekly report lists each finding with its owner and outcome, one takedown still open, and one scope change: the vendor’s code account is added to the watch list.

The owners table did most of the work. Each finding reached a person who had already agreed to act, and the open takedown was the only item carried into the next week.

Evidence a Program Keeps

Each finding type has its own artifacts, such as a page capture, a log entry or a commit hash, and the guides for each area list them. The program keeps the records that tie those artifacts together and show what was decided.

Record Purpose Kept in
Scope register The domains, brands, executives, code organizations and suppliers being protected. Kept by the program owner and reviewed after acquisitions and launches.
Source list Which sources are searched for each area, and how often. The monitoring configuration or the provider’s service description.
Finding record What was found, where, when it was first seen and how it scored. The case system, with the captured artifacts attached.
Confirmation note Who judged the finding real or dismissed it, and why. The same case, written at the time of the decision.
Approval record Who approved a takedown request, a customer notice or an account action. The case, or the approval email filed with it.
Log check result Whether a leaked credential or key was used, and the period searched. Identity provider sign-in logs and cloud audit logs, summarized in the case.
DNS zone export Records that point at deleted cloud resources. The organization’s DNS provider, checked for subdomain takeover risk.
Takedown file Requests sent, to whom, replies received, and the date the content went offline. The takedown tracker or case record.
Closure check Proof that the reset held, the old key fails or the page is gone. A dated retest saved to the case.

Artifacts are captured at once, because a phishing page can vanish within hours and the registrar will usually ask for proof of what it showed. The timestamps in these records also produce the measures in the next section.

Measuring a Program

Finding counts are a poor measure on their own, because better coverage raises them. A program is better judged by how fast confirmed findings are contained and how much of the scope it actually sees.

  • Scope coverage: The share of listed domains, brands, executives, code organizations and suppliers with active monitoring in each area.
  • Time to confirm: The hours from collection to an analyst’s decision that a finding is real and relevant.
  • Time to contain: The hours from confirmation to the protective action, such as a session revocation, a key rotation or a domain block.
  • Log check rate: The share of confirmed credential and key findings followed by a search of the logs for their use.
  • Confirmation ratio: The share of raised findings that analysts confirm, which shows whether the feed is tuned or noisy.
  • Open takedowns: Removal requests still open after an agreed period, listed by registrar, host or platform.
  • Recurrence: Kits, operators or hosting that return after a takedown, which points to infrastructure worth blocking in advance.
  • Found first: The share of impersonation cases the program found before a customer or employee reported them.

Trends matter more than single figures, and a rise in customer-reported cases points back to a gap in collection.

A Program's Opening Month

Within about a month a team can fix the scope, clear the backlog and agree who acts. Most of the effort goes into decisions, because the monitoring itself starts quickly.

  • Week 1, scope: List the domains, brand and product names, logos, official accounts, executives, GitHub and GitLab organizations, and the suppliers that hold data or code.
  • Week 2, baseline sweep: Run every source once across the scope and expect a backlog of old breaches, parked domains and stale repositories.
  • Week 3, triage: Confirm the backlog, close what is old or irrelevant, and act first on anything live: working passwords, unrotated keys and active phishing pages.
  • Week 4, procedures: Agree who approves a takedown, who resets accounts out of hours, who rotates keys, and what customers and staff are told.

Some habits are worth setting at the start.

  • Approvals in writing: A short policy states which actions run at once, such as a domain block, and which wait for approval, such as a takedown request.
  • Official channels published: The real domains, support accounts and app listings are published, so customers can tell them from fake apps and profiles.
  • A monthly scope review: New products, acquisitions, executives and suppliers are added as they appear.

Questions for a DRP Provider

Industry analysts group many different services under this name, so a provider’s own definition is the first thing to establish. The questions below separate a monitoring feed from a service that closes findings.

  • Source coverage: Ask for the named sources in each area, and whether they include Telegram, stealer logs, ransomware leak sites, app stores and APK sites, and commit history on both GitHub and GitLab.
  • Confirmation: Ask whether a person confirms significant findings before they reach the customer, and what evidence comes with each one.
  • Credential follow-up: Ask whether the provider checks if a leaked password still works, searches the sign-in logs for its use, and revokes sessions and resets the password itself.
  • Key follow-up: Ask who tells the owner to rotate a leaked key, and whether anyone searches the logs for its use while it was public.
  • Takedown handling: Ask who sends requests, which destinations are covered, how approval works, and whether removed content is watched for its return.
  • Connection to the SOC: Ask whether findings flow into the same team that watches the customer’s identity, email and endpoint logs.
  • Scope and pricing basis: Ask how domains, brands, executives, repositories and takedowns are counted, and whether any are capped.
  • Records on exit: Ask whether the evidence, takedown history and scope register stay with the customer if the service ends.

For an MSP or MSSP, the same questions apply per client, with one more: whether the service and its reports can run under the partner’s own brand.

Digital Risk Coverage at ThreatDefence

Outside monitoring and the SOC share one platform at ThreatDefence, so a finding on the open internet is checked against activity inside the customer’s environment. The platform automates security monitoring, compliance and cyber risk management, and a 24x7 SOC works the findings.

  • One process for every source: Everything the Brand monitor searches is ranked on one scale and handled the same way, whether it is a cloned site, a leaked key or a stolen login.
  • Hand-offs between agents: A finding from one agent becomes the next agent’s task, whether that is blocking, mapping the attacker’s other domains or preparing a takedown.
  • Checks against the logs: For monitored environments, a leaked password or key is followed into the sign-in and audit logs to see whether it was used.
  • Decisions with people: An analyst confirms significant findings before the customer sees them, and containment and takedowns wait for the customer’s approval under its policy.

MSPs and MSSPs can run the full program for each client under their own brand, starting from the client’s names and domains alone. Brand monitoring lists the sources searched and what happens to each finding.

Frequently Asked Questions

What is digital risk protection in simple terms?

Digital risk protection is monitoring of the internet outside an organization’s own systems for threats aimed at it, followed by action on what is found. It looks for fake domains, sites, apps and profiles, leaked passwords and data, secrets in public code, and weak internet-facing systems. Each confirmed finding ends in a reset, a key rotation, a fix or a takedown.

Where does brand protection fit within digital risk protection?

Brand protection is one part of digital risk protection, focused on impersonation of the organization and its people through domains, sites, apps, social accounts and ads. Digital risk protection also covers credentials and data in criminal sources, secrets in public code repositories, the external attack surface and supplier exposure. Some providers use the names loosely, so the scope should be confirmed in writing.

Is digital risk protection a type of threat intelligence?

No. Threat intelligence describes attackers in general: their campaigns, tools and infrastructure. Digital risk protection is about one organization, and asks whether its brand, credentials, data or code are being used against it. They share sources and feed each other, since intelligence about a phishing kit helps a program spot the same kit aimed at its own brand.

How does digital risk protection differ from attack surface management?

Attack surface management inventories the internet-facing assets an organization owns and finds weaknesses in them. Digital risk protection looks mostly at assets other people control, such as lookalike domains, fake profiles, leaked credentials and code on personal repositories. They overlap on external exposure, and a finding is often more urgent when both show it, such as a leaked password for an exposed gateway.

Which teams take part in a digital risk protection program?

Security usually runs the program, with other teams owning parts of the response. Identity teams handle leaked credentials, developers and cloud administrators rotate keys, legal supports domain disputes and trademark claims, communications warns customers, and finance confirms payment requests. A short ownership table that names who decides, who acts and a deputy for each finding type keeps cases moving out of hours.

Can digital risk protection cover suppliers?

Yes. Key suppliers can be added to the scope by name, so their public repositories, leaked data and lookalike domains are watched along with the organization’s own. NIST’s Cybersecurity Framework 2.0 expects supplier risks to be monitored over the course of the relationship. The contract should say who acts when a finding involves a supplier’s systems.

Does digital risk protection replace the SOC?

No. Digital risk protection finds threats on platforms the organization does not control, and the SOC watches what happens inside its own systems. The two work best joined, because a leaked password or a lookalike domain only shows its real impact when sign-in, mail and proxy logs are checked for use. A finding that leads to use becomes an incident for the SOC to handle.

How does an MSP run digital risk protection for many clients?

An MSP or MSSP keeps a separate scope, approval policy and evidence record for each client, so one client never sees another client’s findings. The client still owns decisions such as takedown approval and customer messaging. Shared intelligence helps every client at once, since a phishing kit or hosting provider seen against one brand can be watched for across all of them.

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.