National ID Number: Data Point Intelligence Guide

A national ID number is the closest thing that exists to a primary key for a human being. It is also the artifact most likely to end an investigation in a disciplinary hearing rather than a report if it is handled carelessly.

Understanding the National ID Number as an intelligence artifact

A national ID number is an identifier assigned to a natural person by a state body: a US Social Security Number, a UK National Insurance Number, an Indian Aadhaar number, a Brazilian CPF, a Nordic personnummer, a South Korean resident registration number. Structurally it is a fixed-length numeric or alphanumeric string, usually with a trailing check digit computed under a published scheme such as Luhn or ISO/IEC 7064. It represents a state's formal assertion that one specific person exists and is distinguishable from every other person on its register.

The analytically important split is opaque versus semantic. Randomised schemes such as post-2011 US SSNs carry no decodable content. Semantic schemes encode date of birth, sex, birth region and a serial, so the number itself is a biographical record. A third category is document numbers found in passport machine-readable zones under ICAO Doc 9303, which identify a booklet rather than a person and are frequently confused with the underlying national number.

Why it matters

It is the strongest deduplication key an investigator ever gets. Names collide, transliterate inconsistently and change with marriage; a national number does not. It collapses name-matching ambiguity across corporate registries, court dockets, sanctions designations and breach corpora into a single deterministic join. Sanctions programmes publish national ID and passport numbers in their identifier blocks precisely because this is the tightest available link between a record in your dataset and a designated individual.

What analysts actually look for

These are the concrete, observable signals that carry weight in this area of work:

• Check-digit validity, which distinguishes a plausibly issued number from a fabricated or mistranscribed one without any external lookup.
• Embedded date of birth and sex fields in semantic schemes, which corroborate or contradict the biographical data claimed elsewhere in the file.
• Encoded birth region or issuance area, which places a subject geographically at the point their identity was registered.
• Format mismatch between the number's structure and the nationality claimed by or for the subject, indicating fabrication or a misfiled record.
• One number attached to several distinct names across datasets, indicating identity theft, synthetic identity construction, or upstream data quality failure.
• One person carrying numbers from multiple jurisdictions, indicating dual nationality, migration history, or deliberate identity layering.
• Presence in the identifiers block of a sanctions or PEP listing, which converts a weak name match into a defensible designation match.
• Appearance as a director or shareholder identifier in registries that publish them, linking a natural person to corporate structures.

Where the data comes from

Authoritative and openly available collection points. Always confirm licensing and terms before operational or commercial use:

• OFAC SDN List — Designated persons with national ID, passport and tax numbers published in structured identifier fields
• UN Security Council Consolidated List — Global designations including national identification numbers, passport numbers and full biographical detail
• EU Consolidated Financial Sanctions List — EU designations with identity documents, ID numbers and issuing authority per listed person
• UK OFSI Consolidated List — UK financial sanctions targets with national insurance, passport and identification numbers where held
• ICAO Doc 9303 — Authoritative specification for machine-readable travel document formats and check-digit calculation
• ISO/IEC 7064 — Standard defining the check character systems used by many national identifier schemes
• World Bank ID4D — Country-by-country documentation of national identity systems, coverage and identifier formats

A working method

A repeatable sequence beats ad-hoc searching. This is a practical starting workflow:

1. Establish lawful basis first — Record the authority, purpose and retention period before the number enters any system. If you cannot state the basis, do not ingest it.
2. Classify jurisdiction and scheme — Determine which national scheme the string conforms to by length, character set and prefix structure before assuming a country of origin.
3. Validate offline — Run the published check-digit algorithm locally. Never validate a live identifier by submitting it to a third-party lookup service you do not control.
4. Decode embedded fields — For semantic schemes, extract date of birth, sex and region, then compare them against the biographical claims already in the case file.
5. Screen against designation lists — Match the number against sanctions and PEP identifier blocks, which give an exact-match link rather than a probabilistic name match.
6. Tokenise for storage — Persist a salted hash or token for joining, keeping the cleartext value in a restricted vault accessible only to named, logged roles.
7. Document provenance — Record where the number came from, who accessed it and when, so the chain of custody survives disclosure or challenge.

How this connects across the intelligence taxonomy

Intelligence work does not respect neat boundaries. The mission domain you are working, the disciplines you practise, and the data points you pivot on are one connected system. These are the direct relationships for this entry — every link is also a tag, so you can follow any thread across the whole library.

Collected by these disciplines

• Geospatial Intelligence — Intelligence Derived from Place
• Identity Intelligence — Resolving and Verifying Who Someone Is
• Criminal Intelligence — Intelligence Supporting Criminal Investigation
• Logistics Intelligence — Cargo, Freight, and Physical Movement
• Human Intelligence — Information from People, Ethically Obtained
• Imagery Intelligence — Interpretation of Visual Imagery

Investigated in these domains

• Border Security & Migration

Pivots to these data points

• Person / Name — A named individual — the subject of identity resolution and profiling.
• Email Address — Electronic mail address tied to an individual or organization.
• Username / Handle — Screen name or handle used across online platforms and services.
• Phone Number — Telephone number for voice, SMS, or messaging identification.
• Physical Address — A physical or mailing address tied to a person, company, or registered entity.
• Social Profile — A social media profile or online account page tied to a persona or identity.

Inside the platform: where National ID Number lives

The Quantus platform is 204 pages behind a 147-item sidebar organised into six working groups: Command (24 items), Dashboards (15), Threat Theaters (14), Intelligence Domains (15), Investigate (34), and Administration (45). This entry is not a page in isolation — it is a thread running through several of them.

The modules that matter most here:

• datapoint.php?dp=dp_national_id — Data point hub
• domain.php?d=border — Border Security & Migration dashboard
• search.php — Advanced search, filter and pivot
• correlate.php — Correlation graph
• cases.php — Case management

Each dashboard is local-first: it renders from the platform’s own database rather than depending on a live third-party call, so it still works when an upstream API is unreachable or rate-limited. Heavy aggregates are cached with a hard query time cap and degrade to the last good value instead of hanging the page.

Automation, playbooks and AI skills

Analysis that only happens when someone remembers to run it is not a capability. The platform ships a 30-step automation pipeline (cron.php) that collects, ingests, resolves, enriches, correlates and scores on a schedule — 25 seeders, 11 resolvers and 7 enrichment runners, all idempotent and cursor-based so a run can be interrupted and resumed without duplicating or losing work.

AI skills that apply

The 16 one-click operations in ai-skills.php are deterministic jobs, not free-text generation. The ones that matter here:

• Enrichment Runner
• Enrichment → Local
• Correlate Infrastructure
• Summarise (Copilot)
• Generate Report

Alerting closes the loop: rules in alerts.php fire on new indicators matching a saved query, so a first sighting in this area raises a notification rather than waiting to be noticed at the next review.

Feeds, data sources and the API

The collection layer runs a feed registry of free, machine-readable sources — bulk blocklists and trackers (Maltrail, IPsum, FireHOL, the full abuse.ch corpora, phishing databases, Emerging Threats, Spamhaus, DigitalSide, ThreatView), authoritative government feeds (CISA KEV, OFAC, UN and EU sanctions lists), and reference datasets (RIR allocations, ip-to-ASN and geolocation tables, MITRE ATT&CK, EPSS). collect.php pulls them server-side on a schedule; feeds.php and source-catalog.php show what is registered, what it covers and when it last ran.

Anything the platform holds is reachable programmatically. The REST API in api.php exposes 11 endpoints — status, stats, search, lookup, recent, export, bulk_check, top_threats, by_category, categories, check — and export.php streams 18 formats in bounded chunks, so a million-row export neither exhausts memory nor times out:

STIX 2.1, MISP, OpenIOC 1.1, CEF (ArcSight), LEEF 2.0 (QRadar), Zeek/Bro intel, Snort/Suricata rules, Palo Alto EDL, BIND RPZ, hosts blackhole, iptables, CSV, JSON, NDJSON/JSONL, XML.

That covers the CTI standards (STIX 2.1, MISP, OpenIOC), SIEM ingestion (CEF, LEEF, Zeek), detection engines (Snort/Suricata), and direct enforcement (Palo Alto EDL, BIND RPZ, hosts, iptables) — so intelligence developed here can be actioned in the tools you already run, without a manual reformatting step. A TAXII 2.1 server and a MISP/RSS feed are also served for pull-based sharing.

Use cases

Three ways this entry earns its keep in day-to-day work:

1. Triage under time pressure. An artifact or report lands and you need a defensible read in minutes, not days. Establish lawful basis first is the first move; the platform pre-computes the enrichment so the analyst spends the time on judgement rather than lookups.
2. Building the picture. A single indicator is rarely the story. Validate offline turns one artifact into a network — shared infrastructure, repeated selectors, the same operator behind different names — via the correlation graph and the cross-entity link engine.
3. Producing something actionable. Analysis that ends in a document nobody can use is wasted. Document provenance feeds the case file, the detection rule, the block list or the referral — with sourcing attached so the recipient can verify it.

Case management (cases.php), watchlists, saved searches and scheduled reports mean the work persists between sessions and survives an analyst leaving the team.

How each sector uses National ID Number

The same entry is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The underlying artifacts are shared — the constraints, outputs and thresholds are not.

🎖 Military and defence

Defence use of national identity numbers is narrow and heavily gated. It appears in force protection vetting of local nationals, base access control, detainee and biometric enrolment records, and personnel recovery casework where a hostage or missing person must be resolved against host-nation registries. The number supports a decision about access, not a targeting decision, and it must never be used to build a population-level register outside a mandated programme. Constraints are severe: status of forces agreements, host-nation data protection law and the risk that a transferred identity list endangers local staff. Analysts feed a vetting adjudication or a J2 identity product, hold the cleartext in a restricted enclave, and record the authority under which each number was collected.

🕵 National intelligence

National intelligence services use these numbers as high-confidence resolution keys inside all-source identity work, joining registry extracts, travel data, sanctions identifier blocks and acquired datasets against a single named requirement. The number is what converts three probable name matches into one confirmed person. Handling is the hard part: numbers acquired under one authority frequently cannot be joined to data held under another, and the classification of a finished identity assessment is usually driven by the collection method rather than by the number itself. Dissemination should carry the tokenised form with the cleartext available only on request through a named custodian. Every product should state the scheme, the validation performed and the residual risk of an upstream data-entry error.

👮 Law enforcement

For law enforcement the number is both an investigative key and an evidential exhibit. Obtaining it from a government register normally requires a production order, a court authorisation or a formal channel such as a national data-protection gateway; acquiring it from a leaked corpus creates a chain of custody problem that defence counsel will attack. Record how the number entered the case, who authorised the query, and what corroboration links it to the suspect in the dock. Check-digit validation and decoded biographical fields are presented as analytical findings, not as identity proof. The number supports charging decisions on identity fraud, benefit fraud and impersonation directly, and elsewhere it functions as the deduplication key that makes a complex indictment coherent.

🔍 Private investigation and corporate security

Corporate investigators encounter national identity numbers in KYC packs, employment files, litigation disclosure and vendor onboarding. A private actor may validate a number's structure offline, may match it against published sanctions identifier blocks, and may verify it through an official service where the subject has consented or where a statutory check applies. A private actor may not query government registers without authority, may not buy the number from a data broker of unverified provenance, and may not use it to compile a profile beyond the engagement scope. Many jurisdictions criminalise unauthorised collection outright. Keep the number out of report bodies, cite it by last four digits or token, and hold the cleartext under a documented retention clock tied to the engagement.

📰 Journalism and OSINT media

Journalists should treat a national identity number as verification material, never as publication material. It is legitimate to use one to confirm that the person in a leaked registry, a court file and a corporate filing is the same individual, and to state in print that identity was confirmed by government-issued identifier. Publishing the number itself exposes the subject to identity theft and, in authoritarian settings, to state retaliation, and it is difficult to defend in any public-interest test. Redact before sharing files with collaborators, strip the field from any dataset published alongside a story, and give right of reply based on the finding rather than by quoting the number back at the subject.

🌍 NGO, humanitarian and human rights

Human rights and humanitarian organisations collect national numbers for beneficiary registration, family tracing, documentation of arbitrary detention and accountability casework. Do-no-harm dominates: a registry of identity numbers belonging to a persecuted minority is a targeting list if it is seized or leaked. Collect only where the number is genuinely necessary to the service or the case, obtain informed consent in the subject's language, store encrypted with offline key custody, and set a deletion date at the point of collection. For accountability work, hold identifiers separately from testimony so that a compromise of one does not identify the source of the other. Staff handling these fields need training and a clear escalation route when authorities demand access.

🎓 University and research

Research using national identifiers almost always requires ethics board or IRB approval, a data management plan and a formal data-sharing agreement with the custodian. The defensible design pseudonymises at source: the custodian applies a salted hash or a study-specific token and the researcher never receives the cleartext. Where linkage across datasets is essential, use a trusted third party who holds the key and returns linked but de-identified records. Publication should report the linkage rate and the validation rules applied, never example numbers, even fabricated ones that could collide with real issued values. Retention and destruction schedules belong in the protocol, and re-identification, including demonstrating that it is possible, needs explicit prior approval.

Playbook: working National ID Number end to end

A repeatable sequence, from the moment the requirement lands to the moment a product is delivered and the case is closed out. Each phase states what you are trying to establish, not merely what to click — the point is a defensible chain of reasoning, not a checklist.

Phase 1 — Authority and purpose gate

Before any number is written to disk, record the legal authority, the specific investigative question it answers, the retention period and the named custodian. If any of those four cannot be stated in a sentence, the number does not enter the system. A good output is a one-page basis note attached to the case file that a data protection officer could sign without further enquiry. Stop here and escalate if the number arrived from a leaked corpus, a data broker or an unattributed tip, because provenance determines whether processing is lawful at all.

Phase 2 — Scheme and jurisdiction identification

Determine which national scheme the string actually conforms to using length, character set, separator convention and prefix structure, rather than assuming the nationality asserted in the file. Many schemes overlap superficially: an eleven-digit Nordic personnummer, a Brazilian CPF and a Turkish TC Kimlik all look similar to an unprepared eye. The output is a recorded scheme identification with the reasoning. If the string matches no published scheme, treat it as a document number, an internal customer reference or a fabrication and say so explicitly.

Phase 3 — Offline structural validation

Run the published check-digit algorithm locally, ISO/IEC 7064 or Luhn or the scheme-specific variant, inside your own environment. Never validate a live identifier by pasting it into a public web calculator or a third-party API you do not control, because that is disclosure. A good output states validated, failed check digit, or scheme has no check digit, which is itself an important finding since some jurisdictions offer no offline validation at all. Failed validation usually means transcription error before it means fabrication.

Phase 4 — Semantic decode where applicable

For semantic schemes extract the encoded date of birth, sex marker, birth region or serial range and compare each against the biographical claims already in the case. Agreement across three independent encoded fields is meaningful corroboration; a mismatch on the date of birth in a scheme that encodes it is a strong fabrication indicator. Record the decode rules used and their source. Note where a scheme has been revised, because rules valid for numbers issued before a reform date do not apply after it and analysts routinely miss the boundary.

Phase 5 — Designation and enforcement screening

Match the number against the identifier blocks of sanctions and PEP listings, which publish national ID and passport numbers precisely to defeat name-matching ambiguity. An exact identifier match is a far stronger designation finding than a fuzzy transliteration match and should be recorded as such, with the list, the version date and the entry reference. Where a match occurs, freeze further processing and route through the compliance or legal function immediately, because sanctions consequences attach independently of your investigative conclusion.

Phase 6 — Tokenisation before enrichment

Replace the cleartext with a salted hash or a vault token before the record joins any analytic dataset. All downstream linkage, deduplication and graph work runs on the token. The cleartext lives in a restricted vault with named-role access and read logging, retrieved only when an external legal process genuinely requires the actual value. A good output is an analytic dataset containing zero cleartext identifiers that still supports every join the investigation needs.

Phase 7 — Controlled cross-registry resolution

Where the number is used to open corporate registry, court or property records, do so through the official channel appropriate to your authority and record each query. Some registries publish officer identifiers, some accept identifier searches only from authorised bodies, and some prohibit it entirely. The output is a resolution table listing each source, the query, the authority relied upon and the timestamp. Stop and seek legal advice before any attempt to query a foreign register directly rather than through a mutual assistance channel.

Phase 8 — Corroboration and confidence statement

Never let the number stand alone as an identity conclusion. Corroborate with at least one independent attribute: a dated document, a registry record with matching address history, a photograph, a signature or a witness statement. Then write the confidence explicitly, distinguishing the number is valid, the number is associated with this name in source X, and this is the person. Those three are routinely collapsed in weak reporting and separating them is the single largest quality improvement available in identity work.

Phase 9 — Data protection impact and review

For any programme processing national identifiers at scale, complete a DPIA before go-live and review it whenever the purpose, dataset or access model changes. Document the necessity test, the proportionality argument, the minimisation measures, the security controls and the residual risk with an accountable owner. Where the assessment shows high residual risk, prior consultation with the supervisory authority may be mandatory. The output is a live document, not a filing exercise, and it should be readable by the people who actually operate the system.

Phase 10 — Retention, deletion and audit

Enforce deletion by automation rather than by policy statement. Each record carries an expiry derived from the purpose recorded at ingestion, and expired cleartext is destroyed with a logged, verifiable action. Periodically audit who read what, and investigate reads without a matching case reference. A good output is an audit report showing every cleartext access mapped to an authorised purpose, and a destruction certificate for the previous period. Stop the programme if the audit cannot produce that mapping.

Phase 11 — Disclosure and reporting discipline

In any product, cite the identifier by token or by masked form. Where disclosure to a court, a regulator or a partner requires the actual value, disclose through the formal route with a record of what was released and to whom. Prohibit re-identification of tokenised data by anyone outside the custodian role and make that prohibition an explicit written condition on every recipient. The final output is a report that supports its identity conclusions without ever printing a live national identity number in a document that will be circulated.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

Source register: what to collect from, and how

Sources are listed with their access model so you can plan around cost and licensing before you build a dependency on them. Open means no account required; registration means a free account or API key; licensed means paid or institutional access. Always confirm current terms — licensing changes, and a source that was free for research may not be free for commercial or evidential use.

Source	Access	What it gives you	How it is used here
OFAC Sanctions List Search	Open	US designations with structured identifier blocks carrying national ID, passport, tax and registration numbers per listed person.	Exact-match screening of a validated number against US designations, converting a weak name match into a defensible designation finding.
UN Security Council Consolidated List	Open	Global designations with full biographical detail including national identification and travel document numbers where held.	Cross-checks a number against UN listings, which member states are obliged to implement, before any onward reporting.
EU Consolidated Financial Sanctions List	Registration	EU designations published with identity document types, numbers, issuing authorities and dates for each listed natural person.	Identifier-level screening for EU exposure, including passport and national number fields that name matching alone will miss.
UK OFSI Consolidated List	Open	UK financial sanctions targets with passport, national insurance and other identification numbers recorded in the identity fields.	Screening for UK sanctions exposure using the exact number rather than transliterated names of non-Latin origin.
ICAO Doc 9303 machine readable travel documents	Open	The authoritative specification for MRZ structure, document numbering, composite check digits and issuing state codes.	Distinguishes a passport booklet number in an MRZ from the underlying national number, a routine and consequential confusion.
ISO/IEC 7064 check character systems	Licensed	The international standard defining MOD 11-2, MOD 97-10 and related check character algorithms used by many national schemes.	Provides the correct validation algorithm for schemes that cite it, so offline validation is defensible rather than approximate.
European Data Protection Board	Open	Guidelines and opinions on lawful basis, special category data, DPIA thresholds and processing of national identification numbers.	Grounds the lawful basis note and the DPIA for any programme that ingests national identifiers in the EEA.
UK Information Commissioner's Office	Open	Regulatory guidance on identifiers, data minimisation, retention and the accountability documentation a controller must hold.	Reference for controller obligations when an investigation holds national insurance numbers or equivalent identifiers.
Companies House	Open	UK registry with officers, persons of significant control and partial identifiers such as month and year of birth.	Corroborates a claimed date of birth decoded from a semantic scheme against an independent official record.
OpenCorporates	Registration	Cross-jurisdiction company records with officer entries that in some registries include national identifier fields.	Finds corporate roles attached to an identifier where the source registry publishes it, without querying registries directly.
ICIJ Offshore Leaks Database	Open	Searchable structured extract of offshore corporate records naming officers, intermediaries and addresses from multiple leak corpora.	Tests whether a resolved individual appears in offshore structures, using name plus corroborated biographical detail rather than the number.
OCCRP Aleph	Registration	Aggregated public records, leaks, registries and sanctions data with entity extraction and cross-dataset search.	Broad identity resolution across registries and watchlists once a subject has been confidently identified.
Have I Been Pwned	Open	Verified breach catalogue with data classes per incident, including whether government identifiers were among the exposed fields.	Establishes whether a subject's identifiers are in circulation without ingesting the underlying breach corpus.
NIST privacy and identity guidance	Open	Federal guidance on identity proofing, de-identification and protection of personally identifiable information in federal systems.	Supports tokenisation design and the argument that a hashed identifier is still personal data requiring controls.

Prefer sources that publish a methodology and a revision history. A dataset that changes silently is a liability in any product that has to survive challenge.

Tooling

Tools commonly used against National ID Number. None of these replace judgement, and each carries its own failure modes — know what a tool infers versus what it observes.

• Offline check-digit validator — A locally executed implementation of the scheme's algorithm. Limitation: validates structure only, so a well-formed fabricated number passes cleanly.
• Format-aware regular expression library — Detects candidate identifiers in unstructured text by jurisdiction pattern. Limitation: high false positive rate against invoice numbers and reference codes.
• Hashing and tokenisation service — Applies a keyed hash so records join without cleartext. Limitation: an unsalted hash of a short numeric space is trivially reversible by enumeration.
• Secrets vault with access logging — Holds cleartext under named-role access with per-read audit. Limitation: only as strong as the joiners and leavers process feeding role membership.
• MRZ parser — Decodes machine readable zones to document number, issuing state and composite check digits. Limitation: parses the booklet, not the person's national number.
• Sanctions screening engine — Matches identifiers and names against designation lists with versioned list snapshots. Limitation: identifier coverage in list data is patchy and inconsistently formatted.
• Entity resolution platform — Deduplicates records using deterministic identifier joins plus probabilistic name and address matching. Limitation: a single upstream data entry error propagates as a confident false merge.
• Data loss prevention scanning — Finds unmanaged copies of identifiers across file shares, mail and repositories. Limitation: pattern-based detection misses identifiers stored in images or non-standard encodings.

AI skills and automation in detail

These are deterministic jobs with defined inputs and outputs, not open-ended prompting. Each is idempotent and cursor-based: interrupt one and it resumes where it stopped rather than duplicating work or losing progress.

• Enrichment Runner — Walks the indicator set through a chosen provider in time-boxed, cursor-based batches that resume rather than restart.
• Enrichment → Local — Materialises enrichment into the local store so dashboards render from your own database instead of a live third-party call.
• Correlate Infrastructure — Builds the cross-entity link graph: shared hosting, reused certificates, overlapping registrants, repeated selectors.
• Summarise (Copilot) — Produces a narrative summary beside the underlying records. It explains; it never creates indicators or assigns attribution.
• Generate Report — Assembles a sourced product from the current case or query, with provenance attached to each element.

A note on the boundary: the only skill that involves a language model is Summarise (Copilot), and it writes prose about records that already exist. Nothing else on this list involves generation of any kind. No indicator, relationship or attribution in the platform originates from a model. See the full skill list.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

• Validate structure before you believe provenance. A number that fails its published check digit almost always indicates transcription error rather than fraud, and chasing a fabricated identity on the basis of a typo has wasted more analyst time than any other single error in identity work.
• Never confuse a document number with a person number. Passport booklet numbers change on reissue and appear in MRZ fields under ICAO 9303, so treating one as a stable personal key produces false negatives when the subject simply renewed their passport.
• Semantic decodes have effective dates. Several national schemes were reformed, randomised or extended on a specific date, so the rules that decode a 1998 number correctly will produce nonsense for a 2015 issuance and confident nonsense is worse than an unknown.
• One number attached to several names is a finding, not a data quality problem. It points to identity theft, synthetic identity construction or a shared registration used by a fraud network, and it deserves a note in the report rather than a silent deduplication.
• Treat the tokenisation boundary as an operational control, not an architecture diagram. The moment an analyst exports cleartext to a spreadsheet to do a quick join, every control you designed stops existing, so give them a tokenised join that is faster than the workaround.
• Distinguish three claims in writing every time: the number is validly formed, the number is associated with this name in a named source, and this is the person in front of you. Collapsing them is the most common cause of misidentification in finished reporting.
• Where a jurisdiction criminalises collection, the useful question is not whether you can obtain the number but whether a corroborated date of birth plus address history achieves the same resolution lawfully. It usually does, and it survives disclosure.
• Re-identification of tokenised data must be a prohibited act with a named owner, not a technical impossibility you claim. Assume any pseudonymised dataset can be re-identified by someone with auxiliary data, and control the behaviour rather than trusting the maths.

Measuring whether it is working

Capability claims should be falsifiable. These are the measures that show whether work on National ID Number is producing anything, and they are worth baselining before you change process or tooling.

• Proportion of held national identifiers with a recorded lawful basis, purpose and expiry date, measured by automated audit rather than self-report. The target is one hundred per cent and anything less is an open compliance finding.
• Ratio of tokenised to cleartext identifier instances across analytic systems, trending toward zero cleartext outside the vault. Rising cleartext counts indicate analysts are working around the tokenised join.
• Percentage of cleartext reads mapped to an authorised case reference in access logs. Unmapped reads are investigated individually and the count of unexplained reads should be zero every review period.
• Automated deletion completion rate against scheduled expiry, with destruction certificates. Records surviving past expiry indicate the retention clock is not actually connected to the storage layer.
• Misidentification rate: cases where an identity conclusion based on an identifier was later corrected, expressed against total identity conclusions. This measures analytical quality rather than throughput.
• Time from sanctions identifier match to compliance escalation, measured in hours. Long tails here indicate screening output is being treated as analytic colour rather than as a legal trigger.
• Number of DPIAs reviewed within the period against the number of material changes to purpose, dataset or access model. A gap means the assessment has drifted away from the live system.

Beware of measuring volume alone. Indicator counts and report counts rise easily and say little; time-to-attribution, proportion of findings that survive review, and how often a product changed a decision say a great deal.

Common pitfalls

• Format collisions are common; a nine-digit number is not automatically a US SSN and may be a valid identifier in another scheme entirely.
• A valid checksum proves arithmetic conformance, not issuance. Synthetic identity fraud pairs structurally valid but never-issued numbers with real names.
• Some jurisdictions reissue or recycle numbers after death or emigration, so a match can join two genuinely different people.
• Masked or truncated values such as last-four fragments are routinely treated as identifiers and produce very high false positive rates at scale.
• OCR and manual transcription errors from scanned documents silently break joins and create phantom second identities in your dataset.
• Breach corpora contain deliberately fabricated identifier columns injected as canary data by the original holder or by the leak's distributor.

Legal and ethical considerations

National identification numbers are among the most tightly regulated personal data classes. GDPR Article 87 lets member states impose specific conditions on their processing, and many jurisdictions criminalise collection or disclosure without authority. Establish and document a lawful basis before ingestion, minimise to the smallest field set that answers the question, encrypt and tokenise at rest, restrict access by named role, log every read, and apply a defined retention and deletion schedule. Never use the number to re-identify individuals outside the authorised purpose or to enrich unrelated datasets.

Data integrity: no fabrication, no drift, no hallucination

Intelligence that cannot be traced back to a source is not intelligence, it is assertion. Everything in this entry — and everything in the platform behind it — is built on a small number of non-negotiable rules.

Provenance on every record

Every indicator carries the source that supplied it, a first-seen and last-seen timestamp, and a sighting count. Where several feeds report the same artifact, each contribution is recorded separately rather than collapsed, so you can see whether a finding rests on one source or twelve. Source attribution travels with the data into every export, so a recipient can audit a claim without asking you for the working.

Nothing is invented to fill a gap

If the platform has no data for National ID Number, it says so. Empty is displayed as empty — never padded with plausible-looking placeholder values, sample records or illustrative examples that a reader might mistake for observations. A dashboard with no rows is a true statement about collection coverage, and it is treated as a gap to close, not a blemish to hide.

Scoring is deterministic and reproducible

Threat scores, reputation grades and risk tiers are computed from stated inputs with fixed weights, not estimated. The same inputs always produce the same output, and the formula is visible rather than a black box. Aggregates are cached with an explicit time-to-live so a figure on screen is never silently stale — and when a heavy query exceeds its time budget the platform serves the last known-good value and labels it, rather than inventing a fresh number or hanging.

Where AI is used, and where it is not

Language models summarise and explain. They do not create indicators, assign attribution or manufacture relationships. No IP address, wallet, hash or identity in the platform originates from a model — every one is ingested from a named feed, resolved from a reference dataset, or entered by an analyst with a source recorded. Copilot output is presented as narrative alongside the underlying records, never in place of them, so a reader can always check the summary against the evidence.

Guarding against drift

Enrichment is additive and timestamped rather than overwriting. Reference data — sanctions lists, allocations, taxonomies — is re-synchronised from the authority on a schedule instead of being edited in place, so local copies cannot quietly diverge from the source of truth. Attribution is recorded with a confidence level and the reporting it rests on, and inferred relationships are labelled as inferred. When a source retracts or corrects, the correction propagates rather than leaving a stale assertion behind.

What this means for you

You can put a finding from this platform in front of a regulator, a court, a board or a partner agency and show where each element came from. That is the standard the tooling is built to — because in this work, being confidently wrong is more damaging than being usefully uncertain.

By the numbers

The taxonomy this entry belongs to is not a marketing list — it is the actual structure of the platform: 52 mission domains, 52 intelligence disciplines and 65 data points, each with a live dashboard behind it. Supporting that: 18 indicator types, 14 playbooks, 16 AI skills, 18 export formats and a 30-step automated pipeline.

This particular entry connects directly to 6 intelligence disciplines, 1 mission domains, 6 closely related entries — every one of them a tag you can follow, and a dashboard you can open.

Questions analysts actually ask

Can I validate a national ID number using an online check-digit calculator?

No. Pasting a live identifier into a third-party web service is a disclosure of personal data to an unknown processor, and in several jurisdictions it is an unlawful transfer. The algorithms are published and trivial to implement, so run them inside your own environment. The same applies to spreadsheet add-ins and browser extensions that call remote APIs. If you must use an external validation service, it should be the revenue or registry authority's own endpoint, used for a documented purpose, with the response and timestamp retained as evidence that the check was performed.

The number appeared in a leaked dataset. Can I use it?

That depends on your authority, not on the number. Law enforcement acting under a warrant or a statutory power may lawfully process material of criminal origin; a private company generally may not, and in some jurisdictions possession alone is an offence. Take legal advice before ingesting the corpus. Where indirect assessment answers the question, prefer it: services that confirm exposure without transferring records avoid the problem entirely. If you do ingest, minimise to the fields you need, restrict and log access, and set a short deletion schedule tied to the specific purpose.

Is a hashed national ID number still personal data?

Yes, in almost every regime. Hashing is pseudonymisation, not anonymisation, because the identifier space is small enough that an unsalted hash can be reversed by enumerating every valid number in the scheme. Use a keyed hash or a vault token with the key held separately, and treat the resulting dataset as personal data with full obligations. The practical benefit is real: tokenisation limits blast radius, supports joins without cleartext exposure, and makes access control enforceable. It does not remove the DPIA obligation or the retention clock.

How much weight can a semantic decode carry?

It corroborates, it does not prove. A number that encodes a date of birth and sex consistent with the rest of the file raises confidence meaningfully, especially when three encoded fields agree. A mismatch is a stronger signal in the other direction and should trigger a fabrication hypothesis. But decode rules are scheme-specific and change at reform dates, regional codes get reassigned, and some schemes reuse serials. State the rule set you applied and its source, and never present a decode as an independent confirmation when it derives from the same string you are trying to validate.

What is the difference between a passport number and a national ID number in practice?

A passport number identifies a booklet and changes on renewal, loss or replacement. A national number identifies a person and generally persists for life. Sanctions listings publish both, in separate identifier fields, and analysts who join on the passport number get false negatives whenever a subject reissued their document. In an ICAO 9303 machine readable zone the document number sits in the second line with its own check digit, and the national number is usually absent entirely. Record which field type you matched on in every finding, because the two support very different confidence claims.

Can a private investigator lawfully obtain a national ID number for a subject?

Rarely by direct means. A private actor may receive it with the subject's informed consent, may see it in disclosure during litigation, may find it in a lawfully published sanctions listing, and may validate its structure offline. A private actor generally may not query a government register, may not induce a public official to disclose it, and should not purchase it from a broker without verifiable lawful provenance. Several jurisdictions criminalise unauthorised collection with no investigative exemption. Where the resolution problem is real, corroborated date of birth and address history usually achieves the same result lawfully.

Should a national ID number ever appear in a finished report?

Not in the body, and not in an appendix that circulates. Cite it as a token, a masked form or a reference to the vault record, and describe the finding in words: identity confirmed against a government-issued identifier held under case reference X. Where a court, regulator or partner agency requires the actual value, disclose it through the formal route and log what was released to whom. This protects the subject if the report leaks, protects your organisation in a disclosure exercise, and costs the analysis nothing, because the number's value is in the join, not in the narrative.

Standards, frameworks and further reading

Work that references a recognised framework is easier to defend, easier to hand over, and easier for a partner to consume:

• GDPR Article 87 permits member states to set specific conditions on the processing of national identification numbers, which is why lawful basis for the same identifier differs across EU jurisdictions.
• GDPR Articles 5, 6, 9 and 35 govern minimisation and purpose limitation, lawful basis, special category data where the identifier reveals protected attributes, and the DPIA obligation for high-risk processing.
• ISO/IEC 7064 defines the check character systems, including MOD 11-2 and MOD 97-10, used by many national identifier schemes and by the LEI, enabling defensible offline validation.
• ICAO Doc 9303 specifies machine readable travel document structure, including the document number and composite check digits that are routinely mistaken for a national personal number.
• NIST SP 800-63 series governs identity proofing and authenticator assurance, and is the reference for arguing that possession of an identifier is not proof of identity.
• Law Enforcement Directive (EU) 2016/680 sets the separate regime for processing personal data for prevention, investigation, detection and prosecution of criminal offences, including identifier handling.
• Convention 108+ of the Council of Europe provides the international baseline for automated processing of personal data and applies well beyond the EU.
• Illinois Biometric Information Privacy Act and comparable state identifier statutes create private rights of action for unlawful collection, which is why US exposure is litigated rather than merely fined.

References

Primary sources and authoritative references for this entry. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

1. Sanctions List Search — US Department of the Treasury, Office of Foreign Assets Control. Searchable designations with structured identifier fields including national and passport numbers.
2. Guidelines and recommendations — European Data Protection Board. Authoritative interpretation of GDPR obligations covering identifiers, minimisation and impact assessment.
3. Doc 9303 Machine Readable Travel Documents — International Civil Aviation Organization. The specification underpinning passport MRZ structure and document numbering worldwide.
4. ISO/IEC 7064 Check character systems — International Organization for Standardization. The standard defining the check digit algorithms used by numerous national identifier schemes.
5. Digital Identity Guidelines — National Institute of Standards and Technology. Federal guidance on identity proofing and assurance levels used as a reference for identity conclusions.
6. Guide to data protection — UK Information Commissioner's Office. Regulator guidance on controller obligations, retention and accountability for personal identifiers.
7. Consolidated United Nations Security Council Sanctions List — United Nations. Global designations including national identification and travel document numbers.
8. Offshore Leaks Database — International Consortium of Investigative Journalists. Structured offshore entity and officer records used for corroborated identity resolution.

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this entry: tokenised storage, offline format validation and automated screening against sanctions identifier blocks, with full access audit. Explore the platform, or browse the rest of the library by following any tag above.