Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Exposure analyst inventorying public domains and digital assets from a monitoring desk

Defensive cyber guide · 10 min

Audit digital exposure before someone else exploits it.

Digital exposure is broader than a technical flaw. Forgotten domains, public accounts, indexed documents and lookalike brands form an observable surface to inventory, assess and reduce.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Inventory before scanning.
  • Observe only public or authorised material.
  • Prioritise by impact and exploitability.
  • Assign every corrective action to an owner.

Step-by-step method

A reproducible path from question to conclusion.

  1. Two colleagues organising separate responsibilities — AI-generated photograph
    1

    Define scope

    List brands, domains, subsidiaries, exposed leaders and essential services. Set boundaries and required permissions.

  2. 2

    Build the public inventory

    Record known sites, subdomains, official accounts, applications, indexed documents and sensitive-role profiles.

  3. 3

    Find gaps

    Look for forgotten assets, inconsistent redirects, obsolete information, lookalike domains and pages disclosing more than needed.

  4. People talking around a table in a cafe — AI-generated photograph
    4

    Assess risk

    Consider ease of misuse, plausible impact, exposure of people and existing controls.

  5. Two people reviewing and annotating a document together — AI-generated photograph
    5

    Remediate and monitor

    Assign an owner, deadline and proof of correction. Then monitor new domains, accounts and publications that change the surface.

See the surface as a system

A secondary domain may lead to an obsolete login page; a public document may reveal a naming convention; a fake account may borrow an executive’s credibility. Combined, minor elements can enable fraud.

Start with assets and relationships, not a generic vulnerability list. Intrusive testing and active scanning remain out of scope without explicit authorisation.

Prioritise what actually changes risk

Public information does not always need removal. Ask whether it helps identify a target, lend credibility to fraud, reach a service or invade privacy.

Treat high-impact, easy fixes first: abandoned accounts, expiring domains, direct contact details, indexed internal procedures or unclear official channels.

Move from snapshot to monitoring cycle

Exposure changes with each launch, hire, supplier and campaign. A dated inventory, owner per asset and regular review make monitoring useful.

Measure completed remediation, response time and ownerless assets. A short maintained table is better than an impressive map that becomes obsolete.

Include the asset lifecycle

A visible asset may be active, transferred, abandoned or merely archived. Separate visibility from current control. Review providers, delegated administrators and recovery with the authorised owner. Removing a main-site link does not establish that the linked service disappeared.

Check remediation at several layers

Define the expected change: source access, content, rights or public link. Closing access and removing search results differ. Record dates and remaining observed copies without redistributing them. Closing a source does not automatically erase copies elsewhere.

Apply the method

Audit your own digital exposure without amplifying it

Inventory material visible without signing in: name variants, old profiles, images, contact details and metadata. Consider combinations: an old programme, photograph and directory entry may jointly reveal an address or routine.

Record exact URL, visible information and practical risk, then classify by control: edit your profile, replace a document you manage or contact a third-party publisher. Removal from a source and delisting from a search engine are separate actions. Check both the actual document and the search excerpt again, recording the time. Do not republish sensitive information in a public report.

Inventory
Search name variants and former identifiers.
Context
Consider combinations revealing location or routines.
Action
Record the page, responsible publisher and request.

Fictional example: association document. A volunteer finds their home address in an old public PDF, asks the association to replace it and checks that the exposed version actually changed.

Try the reasoning

A result shows an old personal address. How should you document it?

Reasoning: Keep URL, observation time and necessary context; seek the publisher’s relevant process without redistributing the address.

CNIL — recoupement d’informations en ligne

Worked example

An old subdomain appears in a public inventory

Fictional teaching case, not a client investigation.

Does the organisation still own the asset, and which action follows?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
A historical source associates a subdomain with the organisation.That source publishes a past relationship.Current relationship and ownership are unestablished.
The authorised internal inventory does not list the name.The asset is absent from the examined inventory version.An undocumented asset or retired service remains possible.
An owner confirms it belonged to a retired provider.A retirement explanation is supplied.Residual references and relevant configurations still require checking.

Conclusion to record

Classify the asset as historical with a retirement check pending. Assign residual-reference review to the technical owner; do not announce compromise from this trace alone.

What would change the conclusion?

Review after documented confirmation of status, configurations and follow-up ownership.

Check your reasoning

Does an absent inventory row establish absence of an asset, or only absence of a row?

· Open the verification log

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. Forgotten asset

Domain, internal owner, purpose and last check.

Limit: An old trace can refer to an already retired service.

2. Indexed document

Public URL, actually visible data and publishing owner.

Limit: Do not bulk-download or bypass access controls.

3. Remediation

Action, owner, deadline and post-removal check.

Limit: Removing a page does not necessarily purge caches and copies.

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.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
Forgotten assetDomain, internal owner, purpose and last check.An old trace can refer to an already retired service.
Indexed documentPublic URL, actually visible data and publishing owner.Do not bulk-download or bypass access controls.
RemediationAction, owner, deadline and post-removal check.Removing a page does not necessarily purge caches and copies.

Common pitfalls

Four shortcuts that weaken the result.

A woman adjusts a curtain in her workspace — AI-generated illustration.

Scanning without permission

Defensive work stays within public observation or explicit authorisation.

A chart being explained with its context document — AI-generated photograph

Confusing visibility with vulnerability

A public trace is not automatically exploitable; context determines risk.

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

Forgetting people

Executives, finance teams and spokespeople can become impersonation vectors.

Two photographic prints being compared during verification — AI-generated photograph

Delivering without ownership

Every fix needs an owner, due date and verification.

Practical questions

Frequently asked questions.

Does a public audit replace penetration testing?

No. It studies observable surface and information risk. Penetration testing requires a technical framework and specific permission.

Should all public information be removed?

No. Balance utility, transparency, duties and risk. Reduction should be targeted and proportionate.

How often should exposure be reviewed?

After material change and according to risk. Sensitive domains, accounts and assets may require continuous or frequent monitoring.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

CERT-FR. Security advisories and defensive guidance; public visibility alone does not prove compromise.

Editorial scope

Published by Internet Intelligence Service on 15 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections

Further reading

Editorial resources on other sites