首页/专题/开源情报

开源情报

开源情报

开源情报将公开信息与具体问题关联起来。核实来源、日期、地点以及各来源的独立性,区分线索与确认结果,并记录调查范围和结论的局限。

OSINTCTIVerification
配有地图、屏幕和档案的无人开源情报工作台
由人工智能生成的编辑插图

本专题内容

Open sources · Threat intelligence · Verification · Attribution · Provenance

实用指南

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.

阅读指南 EN

已保存的标题 · 无法更新 · 最近成功获取时间 : 2026年10月22日 21:23

参考资料:数据、用途与局限

文档核查日期 .

此语言版本的详细参考说明以英语提供。

参考资料:数据、用途与局限
来源与目的已核实的数据或指标使用方法需要保留的局限
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.

深入了解方法 →

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.

深入了解方法 →

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.

深入了解方法 →

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

媒体来源与 C2PA 验证

此语言版本的详细参考说明以英语提供。

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:证据保全

此语言版本的详细参考说明以英语提供。

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

分页:一致性与恢复

此语言版本的详细参考说明以英语提供。

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