Results for “subkey_cipher_text”

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

Overview

IBY_SYS_SECURITY_SUBKEYS is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores cryptographic subkey material used by the Oracle Payments security framework. The table functions as a protected vault of cipher data consumed when payment instrument details — most notably credit card numbers — are encrypted, decrypted, or masked during payment processing. Each row represents a distinct security subkey, identified by the surrogate primary key SEC_SUBKEY_ID and constrained by the unique index IBY_SECURITY_SUBKEYS_U1.

Application code does not normally expose the subkey contents to end users. Instead, the Payments security engine reads this table internally to resolve the key required for a given card or instrument segment. Access is therefore typically restricted to the IBY schema and to privileged database accounts. Because the table anchors dependent records and is itself referenced by foreign keys rather than owning them, its heuristic Data Vault classification is hub-leaning; in a Data Vault model it would most naturally be modeled as a hub keyed on SEC_SUBKEY_ID, with cipher attributes carried on an associated satellite.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• SEC_SUBKEY_ID — the surrogate primary key (IBY_SECURITY_SUBKEYS_PK) and the column referenced by every dependent foreign key. It is also the only documented unique-index candidate (IBY_SECURITY_SUBKEYS_U1), making it both the technical and business-key identifier in the supplied metadata.
• SUBKEY_CIPHER_TEXT — the encrypted subkey material itself. This is the operational payload of the row and is the column whose confidentiality drives the restricted access model.
• USE_COUNT — a counter that tracks how many times the subkey has been applied or consumed. It supports monitoring of key utilization and can inform rotation or re-keying decisions.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column, used to detect concurrent updates to a subkey row.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — record who created and last maintained each subkey and when, providing the standard WHO-column audit trail common to IBY tables.

Common Use Cases and Queries

Direct querying of this table is unusual in a functional context; it is most often reached through join analysis or DBA diagnostics. A typical inventory query identifies subkeys and their consumption level:

• SELECT sec_subkey_id, use_count, last_update_date FROM iby.iby_sys_security_subkeys ORDER BY use_count DESC;
• Locating segments that depend on a given subkey: SELECT segment_id FROM iby.iby_security_segments WHERE sec_subkey_id = :subkey_id;
• Auditing who last touched a subkey: SELECT sec_subkey_id, last_updated_by, last_update_date, object_version_number FROM iby.iby_sys_security_subkeys;

Reporting use cases center on security administration rather than business reporting: confirming that each active segment resolves to a valid subkey, monitoring USE_COUNT growth, and verifying audit-column completeness. Because SUBKEY_CIPHER_TEXT is encrypted, it should never be surfaced in reports; queries should project only identifiers and counters.

Related Objects

The documented foreign-key and referencing relationships identify the following significant dependents and neighbors:

• IBY_SECURITY_SEGMENTS — references this table via SEC_SUBKEY_ID. This is the principal consumer, linking each security segment to its subkey.
• IBY_CREDITCARD — also references this table via SEC_SUBKEY_ID, tying stored credit card records to their protecting subkey.
• IBY_SECURITY_SUBKEYS_PK — the primary key constraint over SEC_SUBKEY_ID.
• IBY_SECURITY_SUBKEYS_U1 — the unique index over SEC_SUBKEY_ID, the documented business-key candidate.
• The IBY Payments schema at large (IBY owner) and the standard WHO audit columns, which link this table to EBS user and session tracking.

No additional views or public APIs are documented in the supplied metadata; joins to this table should be driven from the two dependent tables above using the shared SEC_SUBKEY_ID column.