Palantir "Gotham" Integration & Governance

Principal workflows

• Onboard a source: Each new source is authorized by your organization, profiled by Moraph, and mapped to the Gotham data model you have approved, with quality and marking rules agreed before any data is loaded.
• Check and load: On every run, records are validated, de-duplicated and checked for required markings before loading. Records that fail are held, not loaded, with the reason recorded.
• Resolve held records: Data stewards and trained classifiers work the held records: fixing them at the source, correcting markings under your procedures, or rejecting them, with each decision recorded.
• Trace and review: For any record in Gotham, lineage shows its source, the pipeline version that loaded it, the checks it passed and any decisions made on it, for analysts and oversight staff.

Who uses it

• Intelligence and defense organizations that run Palantir Gotham
• Data owners and stewards responsible for the sources that feed it
• Security and classification management staff responsible for markings
• Analysts who need to trust and explain the data they work with
• Oversight, compliance and inspector general staff who review data handling

Reporting

• Records received, loaded and held by source and run
• Held records by rule, age and decision
• Marking failures by source and type
• Pipeline run health and freshness by source
• Changes to pipelines, rules and mappings
• Lineage extracts for oversight reviews

Features

• Managed pipelines: Moraph builds, runs and maintains the pipelines from each authorized source into Gotham, under version control.
• Source profiling: Each new source is profiled for fields, completeness, identifiers and markings before mapping begins.
• Data model mapping: Source fields are mapped to the Gotham data model your organization has approved, with the mapping documented.
• Quality checks: Required fields, formats, duplicates and references checked on every run, with rules your data stewards approve.
• Marking checks: Records are checked for required classification and handling markings and for consistency between record-level and field-level markings.
• Hold, don't load: Records that fail a check are held with the reason rather than loaded, so problems are fixed before analysts see them.
• Steward and classifier queues: Held records go to the right people: quality failures to data stewards, marking failures to trained classifiers.
• End-to-end lineage: Every loaded record carries its source, extraction time, pipeline version, checks passed and decisions made on it.
• Access mapping: Markings and source rules are mapped to the access controls you approve in Gotham, and the mapping is reviewed with your security staff.
• Pipeline monitoring: Moraph watches runs, volumes and failures, and raises issues before stale or incomplete data reaches analysts.
• Change control: Pipeline, rule and mapping changes are raised, tested, approved through your process and recorded.
• Suggested fixes, human decisions: Where a rule suggests a likely correction, such as a missing marking inferred from the source, a person reviews and decides; nothing is changed automatically.

Integrations

• Palantir Gotham: Checked records are loaded through the integration interfaces Palantir provides for your deployment, mapped to your approved data model.
• Source systems: Authorized sources are connected by file transfer, database extract, message feed or API, as each source allows.
• Cross-domain transfer: Where a source sits on a different network, data arrives through the cross-domain solution your organization has approved, including Moraph's Cross-Domain Solution (CDS) Transfer Agent.
• Identity provider: Moraph's governance tools are reached through your identity provider, with groups mapped to roles.
• SIEM: Pipeline runs, held records, decisions and administrative actions are sent to your SIEM.
• IT service management: Changes, incidents and source requests are tracked in your service management tool, or in Moraph's if you have none.
• Data catalog: Source descriptions, mappings and lineage can be published to the data catalog your organization uses.

Deployment

• Alongside your Gotham deployment: Pipelines and governance tools run in the same environment as your Gotham deployment, on infrastructure your organization authorizes.
• US-hosted service tooling: Where unclassified service tooling is used, it is hosted in Moraph's United States region only.
• Classified networks: Where pipelines run on classified networks, Moraph's cleared staff work under your organization's authority and procedures, scoped in the proposal.

Security and privacy

• Single sign-on: Staff sign in through your identity provider, so your authentication policies apply.
• Role-based access: Data engineers, stewards and classifiers see only the sources and held records their role and clearance allow.
• Encryption and keys: Data in pipelines and holding areas is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.
• Complete audit trail: Every run, check result, decision and change is logged with the person and time.
• Cleared US support staff: Tickets for federal and defense clients are handled only by US citizens with active clearances.
• Your authority on classified networks: Pipelines on classified networks are built and run under your organization's authority and procedures; Moraph holds no accreditation of its own.

Limitations

• Moraph is not Palantir. Palantir owns and supports Gotham, and its own service commitments, roadmap and outages apply.
• Licenses for Gotham are subject to Palantir's terms.
• Moraph does not classify information. Marking checks find missing or inconsistent markings; classification decisions are made by your trained classifiers.
• Checks catch the problems their rules describe. They cannot make a source accurate, and data that is wrong but well formed can still pass.
• Moraph does not decide who may see data. Access controls in Gotham are configured as your organization approves.
• The service does not change Gotham itself or its analytic features; it governs the data that goes into it.
• Authority to collect, retain and use each source, including any information about US persons, is your organization's responsibility and is confirmed before a source is onboarded.
• Moraph does not hold accreditation for classified environments; operations there take place under your organization's authority.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/palantir-gotham-integration-and-governance. Purchasing routes and company information: www.moraph.com/how-to-buy.