Results for “cc_number_hash1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_SECURITY_SEGMENTS is a Payments (IBY) module table in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the segmented, cipher-encoded representations of sensitive payment instrument data—most notably credit card numbers and related authorization credentials—used by Oracle Payments during funds capture and disbursement processing. The table forms part of the IBY payment security framework, which allows card and bank account data to be tokenized, hashed, and split into discrete segments so that full clear-text instrument values are never persisted in the transactional tables.

From a heuristic Data Vault modeling perspective, the FK structure and the presence of descriptive, mutable attributes such as cipher text, encoding scheme, and hash values suggest a satellite-leaning classification. Each row carries a descriptive payload keyed to an upstream security subkey rather than acting as a standalone business hub. The primary key is documented as IBY_SECURITY_SEGMENTS_PK on the column SEC_SEGMENT_ID, with a matching unique index IBY_SECURITY_SEGMENTS_U1 on the same column.

Key Information Stored

The documented physical schema comprises sixteen columns. The most significant are:

• SEC_SEGMENT_ID — Surrogate primary key; uniquely identifies each security segment row.
• SEC_SUBKEY_ID — Foreign key to IBY_SYS_SECURITY_SUBKEYS; the subkey that groups and secures the segment.
• SEGMENT_CIPHER_TEXT — The encrypted payload holding the protected instrument value.
• ENCODING_SCHEME — Identifies the encoding applied to the cipher text.
• CC_NUMBER_HASH1 / CC_NUMBER_HASH2 — Dual hash values supporting card-number matching and verification without decryption.
• CC_ISSUER_RANGE_ID — Foreign key to IBY_CC_ISSUER_RANGES, tying the segment to the card issuer range.
• CC_NUMBER_LENGTH — Length of the original card number, used for masking and validation.
• CC_UNMASK_DIGITS — Number of trailing digits exposed for display purposes.
• SALT_VERSION — Version of the salt applied during hashing, supporting key rotation.
• OBJECT_VERSION_NUMBER — Optimistic locking control for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns tracking row provenance.

The primary key SEC_SEGMENT_ID is a purely synthetic identifier; no alternate business key is documented beyond the unique index on the same column, confirming the segment value itself is not naturally unique.

Common Use Cases and Queries

Typical workloads involve resolving masked card displays, validating a card against stored hashes, and auditing security segment coverage. A representative query joining to the subkey grouping is:

• SELECT s.SEC_SEGMENT_ID, s.CC_NUMBER_LENGTH, s.CC_UNMASK_DIGITS, s.SALT_VERSION FROM IBY.IBY_SECURITY_SEGMENTS s WHERE s.SEC_SUBKEY_ID = :p_subkey_id;
• Hash lookup for card verification: SELECT SEC_SEGMENT_ID FROM IBY.IBY_SECURITY_SEGMENTS WHERE CC_NUMBER_HASH1 = :p_hash AND SALT_VERSION = :p_salt;
• Issuer range reporting: join to IBY_CC_ISSUER_RANGES on CC_ISSUER_RANGE_ID to aggregate segments by card brand or issuing range.
• Audit of stale or unversioned rows: filter on SALT_VERSION or LAST_UPDATE_DATE to identify records requiring re-hashing after a security key rotation.

Because the table holds tokenized values, most reporting is done against derived attributes—lengths, hashes, and salt versions—rather than the cipher text itself.

Related Objects

The most significant related objects, grounded in the documented foreign key structure, are:

• IBY_SYS_SECURITY_SUBKEYS — Referenced via IBY_SECURITY_SEGMENTS.SEC_SUBKEY_ID; parent grouping for segments.
• IBY_CC_ISSUER_RANGES — Referenced via IBY_SECURITY_SEGMENTS.CC_ISSUER_RANGE_ID; defines issuer/card brand ranges.
• IBY_SECURITY_SEGMENTS_PK / IBY_SECURITY_SEGMENTS_U1 — Primary key constraint and unique index on SEC_SEGMENT_ID.
• Oracle Payments funds capture and disbursement routines that consume the IBY security APIs to write and read segments.
• IBY payment instrument and credit card transaction tables that reference secured instrument identifiers resolved through this table.

All access should be performed through supported Oracle Payments APIs wherever possible, as direct DML against the cipher text columns risks corrupting the tokenization integrity maintained across the IBY schema.