These fictional profiles describe recurring goals and constraints for people working with MISP. Use them to discuss workflows, permissions and acceptance criteria. They are not role definitions, claims about particular people, or a ranking of whose work matters most.
Updated for MISP 3.0.0, 3.0_wip commit 99ebee729. The profiles retain their established names for continuity while focusing on tasks rather than demographic detail. A persona’s goal does not automatically grant the permissions or integrations needed to achieve it.
Primary personas
Farrah
Threat intelligence analyst. Farrah turns observations from several sources into a reviewable assessment and a useful set of investigation leads.
Workflow: Search values and accessible occurrences, investigate them in a workspace/graph, structure related observations as objects, and attach sourced taxonomy/galaxy context. Record notes, opinions and relationships separately from the underlying facts. Curate findings in a report or collection, then prepare an explicitly filtered detection export where justified.
Success: Another analyst can follow the evidence and identify uncertainty. A warninglist hit, correlation or model-generated suggestion is reviewed rather than treated as a verdict. See investigating a value.
Adam
Incident responder. Adam needs to understand an incident’s scope, coordinate findings and hand over the evidence behind response decisions.
Workflow: Maintain an event with observation times, objects and an event report. Use proposals or an extended event for separately owned changes, and analyst research for assessment. Link the appropriate response/case-management system through a tested integration; MISP is not by itself an endpoint-remediation system or a complete evidence chain-of-custody process.
Success: Responders can distinguish confirmed activity from hypotheses and share only the intended scope. See incident assessment.
Secondary personas
Tina
Fraud analyst. Tina looks for relationships among infrastructure, transactions and reports while limiting unnecessary exposure of sensitive records.
Workflow: Use suitable object templates and source references, compare accessible values, and record how each relationship was established. Choose distribution and analyst-data scope for the audience; a notice message or taxonomy label does not establish a legal basis or enforce all handling obligations.
Success: A colleague can reproduce the reasoning without receiving unrelated sensitive data. See structured evidence.
Henry
Law-enforcement investigator. Henry needs to exchange relevant technical findings and preserve the provenance and handling limits of case-related observations.
Workflow: Model observed entities and directional links with objects, retain source/time context, and coordinate with the appropriate sharing community. Keep case access, evidence handling and legal authority in the responsible process; an object template or correlation does not establish admissibility, attribution or authorization to collect personal data.
Success: Partners can trace a shared finding without treating MISP as a complete forensic chain-of-custody system. See structured evidence.
Jacob
Security service provider / community operator. Jacob supports several customers or partner communities with different trust and delivery requirements.
Workflow: Establish organisation identities and scoped users/keys, design sharing groups and peer rules, and verify each delivery path. Use delegation only with an understood ownership and publication process. Check protected-event signatures where applicable; a valid signature is not proof that every factual claim is true.
Success: Intended recipients receive usable context and excluded audiences remain excluded. See sharing workflows.
Jay
Risk analyst. Jay needs to explain the relevance and uncertainty of threat information to people making security and resource decisions.
Workflow: Compare source coverage, observed activity and techniques, keep assumptions in reports/research records, and curate the relevant events/clusters for a briefing. Explain what a chart counts and what the available dataset cannot show. Use linked detection/export results as one source of evidence rather than equating indicator volume with organisational risk.
Success: A stakeholder can understand the assessment, its evidence and limits. See reporting a finding.
Sarah
Information-operations researcher. Sarah compares sources and campaign hypotheses without turning a correlation into a claim about intent or truthfulness.
Workflow: Preserve source material and observation times, model relevant entities/links, and use DISARM or another appropriate knowledge collection for technique context. Write reports that distinguish evidence, assessment and open questions, and scope collaboration deliberately.
Success: Other researchers can challenge the reasoning and trace the supporting material. See reporting a finding.
Priya
MISP site administrator. Priya operates the instance and controls infrastructure-level configuration and privileged access.
Workflow: Manage roles and authentication, review grouped settings/health checks, inspect migration and worker state, and maintain backups. Enable recurring tasks, workflow triggers and external integrations deliberately, with monitored failure paths and a recovery process.
Success: Changes are auditable and the instance can be restored. Healthy-looking UI controls are backed by operational checks. See administration.
Marco
Organisation administrator. Marco maintains the organisation’s authorized accounts and supports its day-to-day use of the sharing community.
Workflow: Manage users and keys within the granted organisation scope, coordinate intended sharing/classification practices and request site-level changes through the instance operator. Role editing, global configuration and cross-organisation user management are not automatically available to an organisation administrator.
Success: Colleagues have the access they need without expanding privileges to unrelated organisations. See account management.
Other personas
Malcolm
Integration developer / data scientist. Malcolm builds repeatable processing and research pipelines and needs to understand both the data contract and its limits.
Workflow: Use the installed API and a compatible client with a scoped key, test pagination and retries, and distinguish occurrences from shared component values. Keep training/research exports within the intended scope and retain source/review metadata for automated or assisted analysis. Test workflows/providers in an isolated environment before enabling operational work.
Success: A pipeline produces reproducible, explainable outputs and handles partial failures without uncontrolled duplicates or disclosure. See integration workflows and Developer FAQ.
Use the personas in a review
For a proposed change, choose the relevant task, permitted actor, input, expected saved result and failure/visibility cases. Use the user stories as concrete scenarios. Include keyboard/narrow-screen use and explain what requires an external system or a deliberate publication decision. Evaluate the resulting behaviour rather than the number of features a profile mentions.