Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Cyber monitoring workstation and public digital exposure review

Digital exposure and threat signals

Cyber monitoring: see visible risks before they are exploited.

A defensive review of the public attack surface of an organisation, brand or exposed individual, designed to prioritise risk-reduction measures.

The scope is adjusted to the question, urgency and available material. The aim is to obtain a useful answer without widening the research unnecessarily or collecting information that has no bearing on the decision.

Service
Cyber monitoring and public exposure analysis
For whom
Individuals, executives, organisations and their advisers
Sources
Open, lawful, dated and traceable material
Output
IIS / CYBER · decision-ready report
Request confidential scoping →

Objective

Map exposure and separate urgent signals from noise.

Cyber monitoring observes publicly accessible information only: web assets, lookalike domains, fake profiles, hostile mentions and already visible disclosures.

The report ranks signals by likelihood, potential impact and available response, without penetration testing or access to private systems.

When a point cannot be confirmed, it is identified as an uncertainty or a lead for further verification. This distinction protects the quality of the report and prevents a plausible interpretation from being mistaken for an established fact.

Mission scope

What the analysis can cover.

The following areas can be combined or narrowed depending on the case. Each retained element must contribute to the stated objective and be obtained through a lawful, traceable source.

01

Domains and brands

Lookalike domains, typosquatting, deceptive pages and misuse of distinctive signs.

02

Impersonation

Fake accounts, executive impersonation, approach scenarios and fraud indicators.

03

Public exposure

Visible subdomains, indexed services, accessible documents and disclosed technical information.

04

Visible leaks

Public references to compromised or exposed data, without unlawful acquisition or consultation.

05

Hostile narratives

Campaign signals, amplification, relays, timeline and observable reach.

06

Prioritisation

Ranking by urgency, impact, confidence and recommended remediation effort.

Typical decision questions

Examples of a focused review.

These are illustrative questions, not client cases. Each calls for a bounded scope, dated sources and a clear account of what remains uncertain.

Four people discussing how to organise their group — AI-generated photograph

Which public assets still belong to the organisation?

Compare domains, official accounts and exposed services with their owners. Assets without an owner or confirmed use are kept separate from technical vulnerabilities requiring a different test.

Is a domain or account imitating an official channel?

Compare spelling, destinations, observable history and public communications. The result describes impersonation risk without attributing an operator from shared hosting alone.

Review of a digital-wallet authorization with a security key.

What changed since the last review?

Date new accounts, certificates, indexed documents and visible relays. Assign each change a verification owner and priority tied to plausible impact.

Deliverable

A defensive roadmap based on observable signals.

Findings are connected to concrete action: removal, reporting, security improvements, monitoring, communications or referral to an authorised specialist.

The main findings are written in plain language, with dated sources, confidence levels and practical consequences. A short executive summary supports quick reading, while the detailed sections preserve the reasoning needed to review the conclusions.

ReportIIS / CYBER
  • Exposure map
  • Qualified signals
  • Dated evidence
  • Urgency levels
  • Risk-reduction measures

What to include in your first message

List the public domains or accounts concerned, their expected owners, the observable change and when it was first seen. Identify the team that can confirm whether a service is still in use.

For suspected misuse in progress, alert the team that can protect the account or service. If the incident began with a suspicious email in the United Kingdom, see the NCSC’s reporting guidance.

NCSC guidance on reporting a scam email

Useful distinctions

Clarity about scope protects the decision.

Does a public trace prove identity or intent?

Not automatically. A public trace can be incomplete, outdated, copied, falsely attributed or associated with a namesake. Its value comes from the quality of its source, its date, its context and corroboration by independent elements.

What is outside the scope of a lawful mission?

Accessing private accounts, bypassing security controls, intercepting communications, acquiring unlawfully obtained data or using deception to obtain protected information are excluded. The analysis is confined to open, lawfully accessible sources and client-provided material.

What areas can this analysis cover?

Depending on the question and legitimate purpose, the scope may include: Domains and brands, Impersonation, Public exposure, Visible leaks, Hostile narratives, Prioritisation. Only areas that contribute to the stated decision are retained.

What will the final report contain?

The exact format is agreed during scoping. Available components include: Exposure map, Qualified signals, Dated evidence, Urgency levels, Risk-reduction measures. Findings remain linked to dated sources, confidence levels and explicit caveats.

Can advisers or internal teams use the report?

It is designed to support review with a concise brief, dated sources, confidence levels, caveats and next-step options. The recipient remains responsible for their own legal, technical, HR or communication decisions.

Reading technical evidence

Keep the CVSS vector alongside the score

A score alone hides its assumptions. CVSS v4 separates Base, Threat and Environmental metrics.

Field or situation and its interpretation
Observed itemWhat it means
CVSS-BIntrinsic severity based on Base metrics.
CVSS-BTAlso accounts for Threat metrics.
CVSS-BTEAlso incorporates the specified Environmental context.

Retain version, vector, source and date. Then check product, installed version and exposure conditions before prioritising action.

FIRST — CVSS v4.0 User Guide

Agree the monitored assets and alert thresholds

List domains, official accounts, public documents and responsible owners. Record the observation interval and define which changes merit an alert: new impersonation, sensitive disclosure or unexplained asset change.

What makes the output usable

An actionable alert contains the observed item, time, plausible harm, assigned owner and a proportionate next step. Track acknowledgement and correction; do not present passive public observation as a penetration test.

Primary sources and their limitations

Example of a brief to adapt during scoping

Which unknown public assets require attribution, remediation or documentation?

Authorised scope, known domains, internal owners, expected service status and alert handoff rules. Public research does not replace an authorised technical inventory.

Evidence and decision boundaries
ComponentUseful materialLimit
Asset and relationshipIdentifier, source, observation date and owner to confirm.A shared IP does not prove a shared operator.
Impact and actionExposed data or function, plausible consequence, owner and proposed measure.Separate visible exposure from observed compromise.
ClosureCheck the agreed measure and identify out-of-scope material.Announced correction differs from verified correction.

Handoff to agree: An attributed inventory with unknowns, qualified alerts and remediation owners, without unrelated data collection.

Review trigger: New domain, reappearing document or changed asset owner.

Read a fictional worked case

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. Asset and relationship

Identifier, source, observation date and owner to confirm.

Limit: A shared IP does not prove a shared operator.

2. Impact and action

Exposed data or function, plausible consequence, owner and proposed measure.

Limit: Separate visible exposure from observed compromise.

3. Closure

Check the agreed measure and identify out-of-scope material.

Limit: Announced correction differs from verified correction.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

Agree what closes a finding and what reopens it

These are suggested review criteria to agree during scoping, not a promise of a particular result. Closing a finding does not close every risk in the case.

Acceptance evidence and review triggers
FindingEvidence to agreeReview trigger
A corrected public exposureThe authorised owner confirms source access has changed; search excerpts are checked separately.The original resource becomes accessible again or a distinct copy appears.
An impersonating domainThe exact domain, observation time, impersonated asset and handling owner are recorded.New infrastructure, destination or contact changes the likely impact.
A vulnerability alertInstalled version and applicable vendor advisory are checked by the authorised technical team.Changed exposure, exploitation evidence or an incomplete remediation check.

Confidential scoping

Describe the context in simple terms, without sending passwords, identity documents or unnecessarily sensitive material at the first stage.

Laptop, phone and notebooks on a desk — AI-generated photograph
Scope the mission