What Is Call Detail Record Auditing? (IMSI Logs)

Call detail record auditing is a controlled review of telecom usage records and related IMSI data. It checks whether records are complete, consistent, protected, and handled under an approved purpose. An IMSI is a mobile subscriber identifier, not proof of a person’s identity or location. A sound audit preserves source files, tests them against documented rules, and records every authorized access.

A difficult part of this work is separating a record-quality problem from a conclusion the data cannot support. CDR fields vary by network element, software release, and operator setup. IMSIs are sensitive identifiers, and they may not map neatly to a single person or device. The audit must answer a defined operational or compliance question, not invite broader identity or location inference.

I use “audit” here to mean a documented review of records and controls, not an investigation of an individual. The method below follows the relevant 3GPP standards while leaving legal authority, retention, and access decisions to the organization’s policy and applicable law.

What does CDR auditing with IMSI logs mean?

A CDR audit tests call detail records and associated identifier events against a stated purpose. It checks record structure, required fields, counts, timestamps, integrity, access, and retention. It does not assume every network produces the same fields, or that an IMSI identifies a person. The exact audit rules must match the system and its approved use.

A call detail record (CDR) is a network-generated record of a communications or charging event. It can contain fields such as event times, service details, and identifiers, but the actual content depends on the network and its configuration. CDRs are not necessarily recordings or transcripts of communications.

An IMSI, or International Mobile Subscriber Identity, is a mobile subscriber identifier with up to 15 decimal digits. 3GPP TS 23.003 describes its structure and use. Treat it as sensitive personal data. Do not interpret it as a person’s name, a device’s permanent identity, or a location.

Standards help set a baseline. 3GPP TS 32.297 covers CDR file formats, while TS 32.298 defines charging-data parameters. Use the versions and network-specific documentation that apply to the system under review. A standard does not guarantee that a particular field exists in every export.

Planning: Define audit purpose, authority, and data scope

Planning sets the boundaries before anyone views sensitive records. Write down the audit question, systems, date range, permitted identifiers, legal basis, approved reviewers, and retention period. These limits reduce unnecessary access and help reviewers tell a valid exception from a result that falls outside the audit’s purpose.

Start with a question that can be tested. For example: “Do exported CDR counts reconcile with the approved source report for this date range?” is more useful than “What can we learn from these IMSIs?” Define the expected output before collecting data.

Record the following in an audit plan:

  • The purpose and the authority for access.
  • The network elements and record types in scope.
  • The start and end times, including the timezone used.
  • Which identifiers reviewers may access, and why.
  • The expected record population and comparison source.
  • Approved reviewers, retention limits, and secure disposal steps.

Set a rule for exceptions before analysis begins. For instance, the plan can state that count differences will be reported for review rather than silently corrected. Do not invent a universal tolerance. The acceptable variance depends on the systems, export process, and written policy.

Access and data handling: Control identifiers, exports, and retention

Access controls limit who can see or copy sensitive records. Data handling covers approved export, preservation, transfer, storage, and disposal. Keep the original files unchanged, use least privilege, and document each access. These controls support a defensible audit, but they do not by themselves prove that the source data is accurate or lawfully collected.

Use approved operator systems to export records. Capture export time, source system, schema or software version when available, filters, date range, and the person or service account that performed the export. Keep the original export separate from working copies.

At ingestion, calculate a cryptographic hash such as SHA-256 and store it with the audit evidence. Recalculate it after transfer or processing to check whether the file changed. A matching hash supports an integrity check from that point onward; it does not prove the source created an accurate or authentic record.

ControlWhat to recordWhat it can showWhat it cannot show
Source metadataSystem, export time, filters, schema versionHow the export was producedWhether every source event was captured
SHA-256 hashFile hash and calculation timeWhether file contents later changedSource authenticity or correctness
Access logReviewer, time, purpose, actionWho accessed the audit dataWhether access was legally authorized by itself
ReconciliationCounts and comparison scopeWhether defined totals matchWhy a difference occurred

Apply least privilege: reviewers receive only the access needed for their assigned task. Use separation of duties where practical, such as having one person approve access and another conduct the review. Follow applicable law and organizational rules for retention, transfer, and secure disposal. Avoid keeping working copies “just in case.”

Execution: Preserve, validate, and reconcile CDR/IMSI records

Execution turns the plan into repeatable checks. Preserve originals, document the record format, test required fields, review duplicates and gaps, normalize a separate timestamp value, and compare totals across systems. Keep every test tied to the audit question. Do not change source records to make them match.

1. Acquire and preserve

Export only through approved systems and within the approved scope. Retain the original file unchanged, along with export metadata and its initial hash. Record who transferred the file, when it arrived, and how the receiving team verified it.

2. Confirm the schema

Compare the export with the correct version of TS 32.297 and TS 32.298, plus operator documentation. Check whether expected fields are present and whether values follow the documented format. Do not assume that a field name or encoding has the same meaning across vendors or releases.

3. Check records and timestamps

Test for missing required values, malformed entries, repeated records, and gaps that matter to the audit scope. Preserve each source timestamp and any timezone or offset metadata. Create a separate UTC value for comparison. Also record the clock source and synchronization status if known; two timestamps should not be treated as directly comparable without that context.

4. Reconcile totals

Compare like with like: the same source, event type, date range, filters, and processing stage. Record the total from each system, the difference, and the exact comparison method. If totals differ, document the exception and investigate through authorized channels. Do not delete duplicates or fill gaps in the original data.

TestPractical measureExpected result
File integrityHash at intake and after transferHashes match when file contents are unchanged
Schema checkRequired-field presence and formatMeets documented schema for that export
Count reconciliationRecords in each matched populationExact match, or an explained exception under policy
Timestamp reviewSource time, offset, UTC comparison valueConversion is reproducible and metadata is retained
Access reviewLogged actions compared with approvalsEach access has a documented basis

There is no single universal threshold for “acceptable” missing records, duplicate counts, or clock drift. Define thresholds in the audit plan based on the system’s documented behavior and the organization’s policy. If the source offers no reliable expected count or timing baseline, report that limitation instead of implying a pass.

5. Keep IMSI review within purpose

Use the least detailed view that answers the approved question. If an audit only needs a count by event type, do not expose raw IMSIs without a documented need. Never treat records with different IMSIs as proof of different people. A subscriber may use multiple SIMs, and temporary identifiers may appear in network signaling or related records.

Verification: Document findings, integrity checks, and exceptions

Verification shows what was checked and what the evidence supports. A clear audit trail records reviewer identity, authority, query parameters, export actions, timestamps, test results, and disposition. It also states limits, such as missing clock metadata or an unavailable comparison source. Findings should describe record quality and control performance, not make unsupported claims about people.

For each test, preserve enough detail for an authorized reviewer to repeat it: source file reference, hash, schema version, filters, comparison totals, and the result. Record exceptions separately, with their cause if known, the person who reviewed them, and the approved next step.

A useful finding distinguishes fact from interpretation:

  • Fact: Two matched exports contain different record totals.
  • Interpretation: The difference needs review; the cause is not yet confirmed.
  • Limit: The available source does not establish whether the gap arose during generation, export, or later processing.
  • Disposition: Record the approved follow-up, owner, and closure date.

Do not claim a file is authentic based only on its hash. Do not infer a person’s identity or location from an IMSI or CDR unless a separate, lawful, documented process authorizes that specific use. Close the audit by restricting or disposing of working copies under the agreed retention rules.

Illustrative audit cases and common pitfalls

These examples are fictional and show how to apply the checks without turning an audit into identity or location analysis. Each case starts with a narrow question, uses documented evidence, and reports limits. In practice, the applicable network design, operator procedures, and law may change what an auditor can access or conclude.

Case 1: Counts do not match. A review compares an approved export with a source-system summary for the same event type and period. The totals differ. The auditor first checks filters, date boundaries, and export metadata, then records the mismatch for the system owner. The difference is not “fixed” by editing either source.

Case 2: Timestamps appear out of order. A file contains source timestamps without clear timezone information. The reviewer preserves the original values, records the missing metadata, and avoids presenting a UTC comparison as certain. The finding states that clock or offset details are not available.

Case 3: An identifier changes. Two records contain different subscriber identifiers. The reviewer does not conclude that two people were involved. They document the differing values only if required by the approved audit question, then seek an authorized explanation from the responsible system owner.

Common mistakes include relying on undocumented vendor fields, treating hashes as proof of source authenticity, and retaining raw exports beyond the approved period. Another mistake is widening the search when an expected result is not found. Return to the audit scope and obtain new approval before changing it.

Conclusion and FAQ

A sound CDR and IMSI audit is a controlled test of records and handling practices. It begins with authority and scope, preserves the source, checks documented fields and timestamps, reconciles comparable totals, and records limits. The key next step is to align the audit plan with the applicable 3GPP release, operator documentation, privacy law, and internal policy before accessing records.

What is an IMSI log?

An IMSI log is a record or data extract that includes IMSI values or events associated with them. Its fields and meaning depend on the network and export. An IMSI is sensitive subscriber data, not a person’s name or a direct location label.

What does a CDR audit check?

It checks whether defined records are complete, consistent, protected, and handled under approved rules. Typical tests cover schema, required fields, timestamps, duplicates, totals, access history, and retention.

Which 3GPP standards are relevant?

3GPP TS 32.297 addresses CDR file formats, TS 32.298 describes charging-data parameters, and TS 23.003 specifies identifiers such as the IMSI. Confirm the versions that apply to the network and export.

Is an IMSI the same as a phone number?

No. An IMSI is a subscriber identifier used in mobile networks. It should not be treated as a phone number, a person’s identity, or a device’s permanent identity.

Does a hash prove a CDR file is authentic?

No. A SHA-256 hash can help show whether a file changed after the hash was calculated. It does not prove who created the file or whether the original records were accurate.

Should timestamps be converted to UTC?

Keep the source timestamp and its timezone or offset metadata. Create a separate UTC value for comparison when the source information supports a reliable conversion. Record clock source and synchronization status when available.

What if record totals do not match?

Check that both totals use the same source, event type, date range, filters, and processing stage. Document the difference and refer it through approved channels. Do not alter source records to force a match.

Can different IMSIs be assumed to represent different people?

No. One subscriber may use multiple SIMs, and network systems may use temporary identifiers. Resolve identifier questions only through an authorized, documented process.

How long should audit records be retained?

Use the retention period required by applicable law and organizational policy. Limit access during that period and securely dispose of working copies when retention rules require it.

Who should be allowed to review IMSI-level data?

Only reviewers with an approved role and a documented need for the specific audit purpose. Apply least privilege, log access, and use separation of duties where practical.

(This article was written by one of our staff writers, Garrett Vance. Visit our Meet the Team page.)

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *