Skip to main content

Appendix D — Glossary

Use these definitions to distinguish observations, assessment, access and delivery. They follow MISP 3.0.0, 3.0_wip commit 99ebee729; an integration’s terminology or an older API specification may use the same word differently. Links lead to the detailed procedures.

A–C

Analyst Data

Research records associated with supported MISP targets: Notes hold commentary, Opinions express an assessment, and Relationships state typed links. They retain their own authorship/ownership and visibility rather than rewriting the observed fact. MISP 3.0 also supports value-targeted research. Sharing an event does not automatically make every associated research record visible. See Analyst Data.

API

An application programming interface: the operations, inputs and responses through which a client interacts with MISP. REST endpoints support automation, lookup and sharing; permission, record-visibility and key restrictions still apply. PyMISP is a Python client for that API, not a second MISP server. See Automation & API.

Earlier terminology adapted from Wikipedia’s API entry, CC BY-SA 3.0.

API key

A credential associated with a MISP user. Its expiry, allowed IPs, read-only restrictions and other supported controls supplement the account’s permissions. It is distinct from a browser password, a CustomAuth external key and a remote peer’s configuration. See authentication keys.

Cache

A stored representation used to accelerate lookup or avoid repeating a fetch. Feed/remote-data caches are distinct from fully imported local events, and job Redis storage is another use of Redis again. Cache presence does not prove freshness, local ownership or permission to share. See feed management.

Cerebrate

A companion platform for managing community and organisation information. MISP can use a configured connection to obtain supported organisation/sharing-group definitions. The integration has its own credentials and update process; it does not replace event distribution or the need to verify identities. See connectors.

Collection

A curated resource that references supported elements such as events and galaxy clusters. Its own access and sharing settings do not flatten the members’ visibility or ensure that every recipient receives every referenced item. See Collections.

Community

People and organisations that cooperate on intelligence sharing under agreed practices and trust relationships. An instance, organisation, sharing group and synchronization link are technical structures used by a community; none alone describes its entire governance or membership.

Correlation

A link discovered between relevant matching observations according to the configured engine, types, exclusions and visibility. It is a pivot for investigation, not proof of common ownership, maliciousness, causality or attribution. See value and correlation maintenance.

D–I

Decaying Model

A configurable way to score an indicator’s remaining relevance over time using the supported inputs and parameters. A score informs selection/review; it does not inherently delete the observation, clear IDS or deploy a downstream response. See decaying models.

Distribution

The audience/sharing scope of a supported record. Event, child-record, analyst-data and knowledge scopes have their own rules; tags and publication do not override them. Child inheritance uses stored value 5, while sharing-group distribution needs an actual group. See distribution boundaries.

Event Report

A Markdown report attached to an event, used to explain observations, sources and analysis. MISP element references connect the narrative to the underlying records. Extraction/import and export capabilities depend on the supported action and deployment; a report is not automatically an independent case-management record. See Event Reports.

IDS flag

The attribute’s to_ids flag, indicating intended use in supported detection-oriented exports or selection. It is separate from correlation, distribution and an assessment of maliciousness. An attribute with IDS off remains a usable observation; IDS on does not install a detection rule in another tool. See attribute fields.

Indicators

Patterns or observations selected for a detection or intelligence purpose with enough context to explain their intended use. A string extracted from a report, a warninglist miss or an IDS default does not by itself establish a useful indicator. See detection exports.

IOC

An indicator of compromise: an artefact or pattern that may support identifying intrusion or compromise in context. A domain, hash or address is an observation before its significance has been assessed; the term does not make every occurrence malicious.

J–M

Job

A unit of work and its execution/status record. A SQL job ID and the backend process/job UUID are different identifiers. Waiting, running, successful and failed states require inspection of the actual outcome. See background jobs.

Local tags

Instance-local attachments of tags or galaxy context to supported targets. They allow local classification without asserting a shared change to the owner’s observation. Normal native synchronization excludes local attachments; check manual/format-specific exports separately. A tag definition and one attachment’s local/global scope are distinct. See taxonomy scope.

MISP

The MISP Intelligence Sharing Platform, commonly called MISP. The project’s historical name referred to malware information sharing; its present scope includes broader threat intelligence, observations, knowledge and collaborative analysis. The acronym is also used recursively as “MISP Intelligence Sharing Platform”.

MISP Attribute

One typed occurrence of a value in an investigative context, with its own UUID, category, observation times, flags and access context. It may stand alone in an event or be an object relation. In 3.0, its component values also have shared addresses, which do not replace that occurrence identity. See categories and types.

MISP Event

A container for contextually related observations, objects, reports and other supported records, with a creator/owner context, distribution and publication state. It is not necessarily one confirmed real-world incident. See creating an event.

MISP Extended Events

Separately owned events linked to an original event to contribute additional observations. A combined view remains subject to visibility; extension does not transfer ownership of all the original data. See extended events.

MISP feeds

Sources that MISP can cache, compare or import using a supported format/configuration. Caching context and importing full events have different storage and update behaviour. Review the source’s terms, identifiers, format and quality before enabling it. See feed management.

MISP format

The native data structures and interchange contracts used for MISP records. Consult the MISP format specifications together with the installed implementation and client version. MISP JSON, a STIX export and an arbitrary API response are not interchangeable contracts. See API reference.

MISP Galaxy Cluster

An identifiable knowledge entry within a galaxy, with a UUID, description, metadata, version and supported relationships. An attachment connects that context to an observation using a tag and local/global scope. Shipped and custom tag representations can differ; read the stored identity rather than constructing it from a display label. See galaxies.

MISP GnuPG Key

The instance’s configured OpenPGP key used by supported notification-signing/encryption workflows. Manage it according to the mail deployment’s identity, protection and lifecycle requirements. It is separate from an event-signing key in the protected-event system. See mail settings.

MISP Instance

A deployment of the MISP application, its datastores and configured services. Local versus remote describes the instance from which a request or sharing operation is being considered; a connected instance is not automatically entitled to every local record. Files/object storage, caches and external providers also matter when operating or backing up the service.

MISP modules

A companion service providing supported enrichment, import, export or other module operations. The service, module dependencies, configuration and provider access must be present for a particular action to work. A module result is a sourced claim requiring interpretation, and a live lookup can disclose submitted data to a provider. See Modules.

MISP noticelist

A definition that supplies informational guidance on supported entry forms. In the pinned implementation, attribute-form checks use category/type triggers. It is not an arbitrary value-matching engine, an automatic access policy or proof of compliance. See notice lists.

MISP Objects

Structured observations composed of attributes with named object relations, based on an object template. Each instance/attribute retains its own identity and context. Template requirements can allow a single-attribute object; object references declare directional links to observed entities. See MISP objects.

MISP Sightings

Records associated with an observed value/attribute context, such as a positive observation, false-positive claim or expiration claim, with source/time information as supported. They inform assessment; they do not automatically validate a threat or change every IDS flag. See Sightings.

MISP Taxonomies

Controlled classification vocabularies expressed through machine tags: a namespace and predicate, optionally with a value. Their handling/classification meanings are separate from an access grant. Enable the intended vocabulary and tags, then choose the attachment scope. See Taxonomies.

Earlier terminology adapted from Wikipedia’s Taxonomy entry, CC BY-SA 3.0.

MISP warninglists

Lists whose enabled matching rules identify values that merit contextual review: for example, known infrastructure or potential false positives. A hit is not a universal benign/malicious verdict. Warning display and export filtering can have different scopes. See Warning Lists.

N–O

NIDS

A network intrusion detection system, such as a compatible Snort/Suricata deployment. A MISP export must fit that system’s format and operational policy; generating a ruleset does not establish that it was deployed or is effective.

Object template

A definition of relation names, attribute types, constraints and presentation for an observed object. Its UUID/version identify the template, not a particular observation. Updating the catalogue does not silently migrate every saved instance. See object templates.

Observable

Something observed, such as a file, address or activity, represented with the data model and context appropriate to the source. Other standards use the term in their own schemas. It is not an exact synonym for “MISP attribute with IDS off”; observations can be represented by several attributes or an object, and detection use is a separate decision.

Occurrence

One attribute record in its event/object context, identified by its attribute UUID. Several occurrences can share component values while retaining different sources, times, roles, ownership and visibility. See 3.0 values.

Org Admin

An organisation administrator, with the account-management scope granted by the role and applicable organisation checks. This is distinct from site administration. The title does not grant global role editing, server configuration or unrestricted access to other organisations. See administrative access.

Organisation

A local or known remote organisational identity, with a UUID used in sharing relationships. Local database IDs are instance-specific. Creator/owner identity, membership in an organisation and membership of a sharing group answer different questions. See organisation identities.

OSINT

Open-source intelligence: information collected from publicly available sources and used in an intelligence context. “Open” describes source availability, not open-source software, redistribution rights or verified accuracy.

Earlier terminology adapted from Wikipedia’s Open-source intelligence entry, CC BY-SA 3.0.

P–R

Pivot path

A sequence of links followed during an investigation, such as accessible occurrences, correlations or declared relationships. A path records navigable context, not a chain of proof.

Pivoting

Moving from a starting observation to relevant accessible context. In 3.0 this can include value views, workspaces, graphs and knowledge entries as well as event-to-event correlation. See investigation workflows.

Proposals

Suggested attribute additions or changes for an owner/reviewer to assess through the supported proposal workflow. Acceptance changes the relevant data and requires the appropriate rights. An attribute proposal is distinct from a separately owned extended event or a complete object-template proposal. See the proposal FAQ.

Protected event

An event using the supported cryptographic signing/protection mechanism. Verification concerns the signed material and the trusted signing identity; it does not prove the truth of every assessment or widen distribution. See cryptographic keys.

Publishing

A deliberate event release/state transition performed with the relevant permissions and checks. It makes an eligible event available to supported sharing/notification processes; it does not make private data public or bypass distribution. Unpublished data can still be visible locally and accessible to an authorized API/export selection. Mail and peer delivery depend on their configuration and results. See publication.

Pull

Retrieving eligible data from a configured remote instance using the relevant credentials, rules and update/checkpoint behaviour. It is not a guarantee of downloading every record the remote instance stores. See push and pull.

Push

Sending eligible data to a configured remote instance, subject to identities, publication, distribution, filters and the recipient’s accepted contract. A successful connection test does not establish that a particular record was delivered. See synchronization checks.

RESTful

An interface style based on representations of resources and HTTP operations. In MISP, endpoint-specific routes, parameters and response shapes remain part of the actual contract; calling a service “RESTful” does not make every action or format interchangeable. See API reference.

Earlier terminology adapted from Wikipedia’s Representational state transfer entry, CC BY-SA 3.0.

Roles

Local permission definitions assigned to users. They control capabilities alongside access levels, dynamic checks and resource limits; record-level visibility and ownership still matter. Role IDs are local database identifiers, not universal labels for privileges. See roles and ACL descriptors.

S–T

Scheduled Tasks

Configured recurring operations with an interval, next execution, action and execution user. The 3.0 task scheduler discovers due tasks and queues work; a saved schedule is distinct from a running scheduler or a successful job. See recurring tasks.

Sharing groups

Reusable distribution scopes combining the intended organisation and server memberships with their sharing rules. They can include local and remote organisations, and must account for relay/hosting trust. A group is not an end-to-end secrecy channel through an excluded host. See sharing groups.

Site admin

A user whose role grants site administration for instance-wide operations, such as global settings and role/account management. Treat this as privileged access, separate from ordinary organisation administration; resource-specific/dynamic checks can still apply. See administrative access.

Standard MISP Install

An installation following the supported process for its chosen deployment/release. Filesystem, container and orchestrated deployments can have different paths and service identities; the phrase does not imply a universal /var/www/MISP layout or dependency set. See deployment choices.

Sync User

An account used by a peer connection with the required API/synchronization permissions and intended organisation identity. Its key and applicable account state must allow the requested operation. Connection, owner identity and sharing rules still need verification. See sync identities.

Synchronisation

The exchange of supported data and updates between instances through configured push/pull mechanisms. Native MISP synchronization, feed import and TAXII integration have different contracts and scopes. See sharing options.

Tagging

Attaching classification/context labels to supported records with the appropriate permission and local/global scope. A tag can be used in a filter or configured automation policy; its presence alone does not trigger every action, change IDS or grant access. See taxonomy use.

Templating

Using definitions/forms to guide structured entry. Object templates describe relations and constraints; event-entry templates/forms are a different mechanism. A template is separate from the observed instance created with it. See object authoring.

V–W

Value

A stored component value used across attribute occurrences in MISP 3.0. A composite attribute can have separate component values. Equal stored values do not merge occurrences or establish their interpretation, ownership or visibility. See value identities.

Value address

The SHA-256 address MISP assigns to a stored normalized component value. Use the returned address rather than hashing an unnormalized input. It is distinct from a file-hash attribute, an occurrence UUID, an event UUID and an access grant. See value APIs.

Worker

A managed process consuming the intended background-job queue. In 3.0, ordinary queue workers use start_worker; the recurring-task poller uses scheduler_worker. Supervisor process state, Redis reachability and job completion are distinct checks. See background processing.

Workflow

An automation graph connecting supported triggers, conditions and actions. Blocking and non-blocking execution paths differ; a graph/blueprint alone does not enable every trigger or provider. Workflows are distinct from recurring task schedules. See Workflows.

Workspace

A 3.0 research context for organizing and exploring supported graph elements and relationships. Its saved state and visibility are separate from ownership/distribution of the underlying records. A layout or edge is an investigative aid rather than evidence of causality. See investigation workflows.

Maintaining this glossary

Use a concise definition and a link to the relevant procedure. Distinguish terminology from specific deployments, avoid claiming automatic enforcement without a configured mechanism, and retain source/licence attribution for adapted material. A broad term does not prevent adding a more specific term in this Quarto glossary.