Home/Explore topics/OSINT & intelligence

OSINT & intelligence

OSINT & intelligence

OSINT, or open-source intelligence, turns accessible information into verifiable conclusions for a defined question. It combines documentary research, entity mapping, timelines and provenance checks. This topic explains how to distinguish independent sources, repetitions and hypotheses without confusing public availability with unrestricted reuse.

OSINTCTIVerification
Empty OSINT desk with maps, monitors and an intelligence dossier
AI-generated editorial illustration

What makes an open source useful for a decision? Its origin, context and limits can be explained. Public access guarantees neither authenticity nor permission to reuse. Preserve the original document, access date and reasoning connecting its contents to the question.

Distinguish an account’s identity, a publication’s author and an infrastructure owner: these may differ. A matching name, shared technical address or visual resemblance remains a lead requiring corroboration. To avoid circular confirmation, trace the earliest publication and identify sources that merely repeat it.

In this topic

Open sources · Threat intelligence · Verification · Attribution · Provenance

Practical guides

Verify a claim using open sources

How do you verify an open-source claim? Define a precise assertion, trace its earliest publication and seek evidence of different kinds. The expected output is an evidence record covering the claim, original URL, event date, access date, context, supporting material, contradictions and justified confidence. Missing information does not automatically establish that an event did not happen; repetition is not independent confirmation.

Read the guide

Intelligence watch

Open the news desk →

Saved headlines · source refresh unavailable · Last successful fetch : Oct 22, 2026, 9:24 PM

References: data, uses and limitations

Documentation reviewed on .

References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
FIRST · Traffic Light Protocol

Indicate who may receive redistributed information.

TLP 2.0 uses RED, AMBER, GREEN and CLEAR; AMBER+STRICT restricts sharing to the recipient organisation. Labels must not be translated. Keep the marking with the information and check recipients before forwarding. Ask the source to clarify any ambiguity.

Explore the method →

TLP is neither a formal classification nor a reuse licence. It does not guarantee content accuracy.
C2PA · Content Credentials

Describe and verify certain content provenance information.

C2PA specification 2.4 defines manifests, assertions and cryptographic binding mechanisms associated with media. Examine what the manifest asserts, who signed it and whether validation succeeds. Test preservation after transformations and distribution.

Explore the method →

Validated provenance does not establish the truth of a scene. Absence of a manifest does not demonstrate a fake.
ICANN · Registration Data Lookup

Consult available domain registration information.

RDAP is the registration data access protocol. ICANN Lookup provides access to available public registration data. Keep the exact domain, consultation date and result. Distinguish registrar, technical service and the entity operating a website.

Explore the method →

Data may be redacted or limited. Domain information alone cannot attribute content or an operation to a person.

Media provenance and C2PA validation

Separate technical trace, source and judgment

Verifiable provenance helps describe a file’s history. Analysts must still check contextual claims and the independence of documents repeating them.

  • Associate each claim with its exact asset and source.
  • Trace repetitions to origins before describing corroboration.
  • Retain uncertainty and information that could change the judgment.

Open the C2PA explorer and publication cases →

References consulted on · C2PA · Content Credentials Explainer ODNI · ICD 203, Analytic Standards

OSINT: evidence preservation

Usable intelligence retains the trail of its supporting material

Connect each conclusion to sources, preserved objects and working transformations. Custody complements corroboration; it does not turn unverified information into established fact.

  • Describe observed scope, capture limits and date uncertainty.
  • Separate preserved reference, technical copy and assessment extract.
  • Expose unconfirmed transfers and analytical assumptions.

See copy lineage and the eight preservation cases →

Sources reviewed on · NIST · Digital Evidence Preservation · NIST IR 8387 · Full report · NIST · SP 800-86 · NIST SP 800-86 · Full report · NIST · FIPS 180-4 · Secure Hash Standard

Pagination: consistency and recovery

Reconcile collection identities and revisions

An exit inventory or OSINT collection can reach the last page while missing an object or mixing its revisions. A total alone does not establish that expected data is present.

  • Fix order, scope and consistency reference before reading.
  • Compare IDs and revisions beyond row counts.
  • Retain discrepancies and recovery decisions when the reference changes.

Compare computed reads and recoveries →

Sources reviewed on · Google · AIP-158 Pagination · PostgreSQL 18 · LIMIT and OFFSET · PostgreSQL 18 · Row constructor comparison · PostgreSQL 18 · Transaction isolation · OWASP · API1:2023 Broken Object Level Authorization