MISP × Ambacti

Bring MISP into
the flow of work.

A little less busywork with MISP.

Roman aqueduct developing from a precise architectural drawing into marble.
Gather contextDo the workReview & share
Attribute6 capabilities
  • Get many attributes
    Read
  • Get an attribute
    Read
  • Get a filtered list of attributes
    Read
  • Create an attribute
    Write
  • Delete an attribute
    Write
  • Update an attribute
    Write
Event8 capabilities
  • Get many events
    Read
  • Get an event
    Read
  • Get a filtered list of events
    Read
  • Create an event
    Write
  • Delete an event
    Write
  • Publish an event
    Write
  • Update an event
    Write
  • Unpublish an event
Feed6 capabilities
  • Get many feeds
    Read
  • Get a feed
    Read
  • Create a feed
    Write
  • Disable a feed
    Write
  • Enable a feed
    Write
  • Update a feed
    Write
Galaxy3 capabilities
  • Get many galaxies
    Read
  • Get a galaxy
    Read
  • Delete a galaxy
    Write
Noticelist2 capabilities
  • Get many noticelists
    Read
  • Get a noticelist
    Read
Object1 capabilities
  • Get a filtered list of objects
    Read
Organisation5 capabilities
  • Get many organizations
    Read
  • Get an organization
    Read
  • Create an organization
    Write
  • Delete an organization
    Write
  • Update an organization
    Write
Tag4 capabilities
  • Get many tags
    Read
  • Create a tag
    Write
  • Delete a tag
    Write
  • Update a tag
    Write
User5 capabilities
  • Get many users
    Read
  • Get a user
    Read
  • Create a user
    Write
  • Delete a user
    Write
  • Update a user
    Write
Warninglist2 capabilities
  • Get many warninglists
    Read
  • Get a warninglist
    Read
Event Tag2 capabilities
  • Add a tag to an event
    Write
  • Remove a tag from an event
    Write

Frequently asked
questions.

What could an Ambacti integration do with MISP?

The documented operations include Attribute: Get many attributes; Attribute: Get an attribute; Attribute: Get a filtered list of attributes; Event: Get many events.

Could I keep a workflow read-only?

For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.

Will every action run automatically?

Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in MISP?

Decide which work could run on its own and which steps need your review.