[adulau]

An identified database or datastore, including type, lifecycle, size and optional embedding model context. Use separate objects for servers, queries and data classification.

service describes a network service and ftm-Table a FollowTheMoney data table; neither models an identified operational database or vector datastore.

Existing templates considered: service, ftm-Table, query.

Use related-to references to service, cloud-resource, identity-group and query objects, preserving the relationship of each query to its database.

OCSF mapping

• database in OCSF 1.9.0 (versioned source)

MISP object relation	OCSF source path
database-id	database.uid
name	database.name
type	database.type
description	database.desc
size-in-bytes	database.size
embedding-model	database.embedding_model
created	database.created_time_dt
modified	database.modified_time_dt

Datetime relations use ISO 8601. Importers can prefer the OCSF _time_dt sibling, or convert the corresponding _time epoch milliseconds to a UTC datetime. Unreported booleans remain absent. Source codes, identifiers and strings keep their source meaning; this template is a CTI-oriented subset of the OCSF object.

All attributes default to to_ids: false. Descriptive metadata, local identifiers, counts, flags and timestamps disable correlation; typed network indicators, package URIs and hashes retain correlation where applicable. Nested entities use MISP object references. Source arrays are marked multiple only when their entries can be represented independently.

Example values

These are object-relation/value pairs for one object, with illustrative identifiers:

{
  "database-id": "db-123",
  "name": "customer-records",
  "type": "Relational"
}

Validation

• ./jq_all_the_things.sh and ./validate_all.sh passed on the baseline plus all 29 proposed templates: 483 template definitions, relationship checks, 22 unit tests and unique UUID checks.
• This template passed JSON Schema validation, required-field reference checks and exact jq -S -j formatting checks against the same baseline.
• The example loaded and serialized with PyMISP 3.0.0 in strict mode.

This PR adds one version-1 template with a fresh UUID, based directly on main at a9c09f216032bc6093d09f68c743cda2dae29aac. It is part of a review of all 190 base OCSF 1.9.0 objects, compared with the 454 existing MISP templates. The review identified 29 new template proposals; existing-template extensions are recorded separately for future work. No live MISP server round-trip was performed.

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-09T16:32:03.034808Z	cb8d95d	PR opened
🔒 Security Review	✅ Completed 2026-11-09T16:31:29.249702Z	cb8d95d	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.