Security Master
The reference database of all investable securities — containing identifiers (CUSIP, ISIN, SEDOL), instrument type, issuer, pricing data, corporate action history, and the classification hierarchies that enable portfolio analytics and compliance checking.
Why This Object Matters for AI
AI cannot value portfolios, run analytics, or check compliance without a clean security master; without it, 'what is this security and how do we price it' varies across systems creating reconciliation nightmares.
Investment Management & Portfolio Operations Capacity Profile
Typical CMC levels for investment management & portfolio operations in Financial Services organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for Security Master. Baseline level is highlighted.
Security Master information lives in scattered sources with no centralized reference. A trader asks 'what's the CUSIP for the new Apple bond issue?' and someone looks it up on Bloomberg. Pricing comes from one vendor, corporate actions from email alerts, and risk classifications from the PM's memory. There is no single Security Master — each desk maintains its own informal reference list.
None — AI cannot perform security valuation, risk classification, or compliance screening because no machine-readable Security Master exists to reference for instrument attributes.
Create any written record of investable securities — even a spreadsheet listing identifiers (CUSIP, ISIN), instrument type, issuer, and basic pricing source per security.
A Security Master spreadsheet exists with columns for CUSIP, ISIN, ticker, issuer name, instrument type, and last price. An operations analyst maintains it by manually adding new securities as they are traded. The Security Master has 3,000 rows but no validation — duplicate CUSIPs, inconsistent issuer names ('Apple Inc' vs 'APPLE INC' vs 'Apple'), and prices that haven't been updated in months for illiquid holdings.
AI could read the exported spreadsheet, but cannot reliably match securities across inconsistent identifiers or trust pricing values that may be stale or incorrectly entered.
Standardize the Security Master format with consistent fields — primary identifier (CUSIP), secondary identifiers (ISIN, SEDOL), canonical issuer name, instrument classification, pricing source, and corporate action flag — with validation rules preventing duplicate entries.
The Security Master is maintained as a standardized database table with consistent fields: CUSIP, ISIN, SEDOL, ticker, canonical issuer name, instrument type (equity/fixed income/derivative), sector classification (GICS), currency, country of risk, and pricing source designation. New securities are added through a template form that validates identifier format and checks for duplicates. However, attributes like credit rating, duration, and corporate action history are maintained in separate unlinked files.
AI can search and retrieve Security Master records by any identifier, but cannot programmatically access risk attributes or corporate action history without separate manual lookups in disconnected reference files.
Migrate from a flat-file Security Master to a reference database where each security attribute — identifiers, classification, pricing, risk metrics, corporate action history — is stored as a discrete, relationally linked field.
The Security Master is a relational database with discrete fields for every attribute: CUSIP, ISIN, SEDOL, instrument type, issuer entity, GICS sector/industry, credit rating, duration, maturity date, coupon rate, dividend schedule, corporate action history, and risk classification. The system enforces referential integrity — an issuer entity links to all its outstanding securities, and a corporate action links to all affected CUSIPs. Required fields are validated on entry.
AI can query the Security Master by any attribute combination, retrieve complete security profiles for valuation, run sector exposure analysis across portfolios, and cross-reference corporate actions with position impacts.
Add formal entity relationships linking Security Master records to pricing vendors, exchange listing data, regulatory classification databases, and issuer fundamental models — creating a queryable security knowledge graph.
The Security Master is a schema-driven reference entity with explicit relationships to pricing vendors, exchange listings, regulatory classifications (SEC, ESMA), issuer fundamental models, and derivative underlying chains. Each security has a machine-readable definition including structured corporate action lineage (spin-offs traced to parents, merger successors linked to predecessors). An AI agent can ask 'what are all outstanding fixed-income securities from issuers in the energy sector with credit rating below BBB and maturity within 3 years?' and get a complete answer with pricing, duration, and covenant data.
AI can perform fully automated security screening, best execution venue selection, corporate action impact assessment, and compliance classification without human reference lookup for any investable instrument.
Implement real-time security reference generation — Security Master records that auto-create from exchange listing feeds, auto-update from pricing vendors, and auto-process corporate actions as events occur.
The Security Master is a living reference entity that generates and maintains itself from authoritative market sources. When a new security is listed on an exchange, a record auto-creates with identifiers, classification, and pricing source. When a corporate action is announced, the system processes the event and updates all affected securities — stock splits adjust share counts, mergers create successor records, tender offers flag affected positions. The Security Master is a real-time reflection of the investable universe, not a manually maintained reference file.
Fully autonomous security reference management is possible. AI can discover new securities, classify instruments, process corporate actions, and maintain a complete investable universe without human reference data entry.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on Security Master
Other Objects in Investment Management & Portfolio Operations
Related business objects in the same function area.
Investment Portfolio
EntityThe managed container of investment positions for each client or fund — containing holdings, asset allocation, benchmark assignment, investment policy constraints, performance history, and the rebalancing thresholds that trigger portfolio adjustments.
Investment Policy Statement
EntityThe formal documentation of investment objectives and constraints — containing return targets, risk tolerance, time horizon, liquidity needs, tax considerations, and the asset class restrictions that govern how each portfolio should be managed.
Trade Order
EntityThe instruction record for each investment trade — containing security, side (buy/sell), quantity, order type, price limits, execution instructions, compliance checks passed, and the lifecycle status from initiation through fill and allocation.
Research Signal
EntityThe quantitative or qualitative investment signal derived from research — containing signal type (fundamental, technical, sentiment), signal strength, affected securities, expiration, and the backtest performance that establishes signal validity.
Performance Attribution
EntityThe decomposition of portfolio returns into contributing factors — containing allocation effect, selection effect, currency effect, and the factor exposures that explain why performance differed from benchmark.
Tax Lot Record
EntityThe cost basis tracking record for each security purchase — containing acquisition date, purchase price, adjusted cost basis, holding period, and the unrealized gain/loss that drives tax-loss harvesting and lot selection decisions.
Manager Due Diligence Record
EntityThe evaluation record for each external investment manager considered or hired — containing investment process assessment, operational due diligence findings, performance track record, fee analysis, and the ongoing monitoring results that determine retention.
Rebalancing Rule
RuleThe codified logic that determines when and how portfolios are rebalanced — including drift thresholds, rebalancing frequency, tax-aware constraints, minimum trade sizes, and the priority rules when multiple rebalancing needs compete for limited trading capacity.
Investment Guideline Compliance Check
ProcessThe automated workflow that validates trades and positions against investment policy constraints — including pre-trade compliance checks, post-trade verification, exception handling, and the override approval process for intentional breaches.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.