Flashpoint Ignite

Version: 1.0.0

Flashpoint Ignite is a threat intelligence platform that provides security teams with data, intelligence, and analytics to help them identify and respond to cyber threats, vulnerabilities, and physical security risks.

Connect Flashpoint Ignite with LogicHub

  1. Navigate to Automations > Integrations.
  2. Search for Flashpoint Ignite.
  3. Click Details, then the + icon. Enter the required information in the following fields.
    • Label: Enter a connection name.
    • Reference Values: Define variables here to templatize integration connections and actions. For example, you can use https://www.{{hostname}}.com where, hostname is a variable defined in this input. For more information on how to add data, see 'Add Data' Input Type for Integrations.
    • Verify SSL: Select option to verify connecting server's SSL certificate (Default is Verify SSL Certificate).
    • Remote Agent: Run this integration using the LogicHub Remote Agent.
    • API Key/Token: API key for Flashpoint Ignite Platform. It should have all the necessary permissions.
  4. After you've entered all the details, click Connect.

Actions for Flashpoint Ignite

List Notifications

Retrieves a list of all notifications.

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Query IDsJinja-templated text containing IDs of queries, comma-separated list. Example : id1,id2,id3Optional
Asset IDsJinja-templated text containing IDs of assets, comma-separated list. Example : id1,id2,id3Optional
OriginJinja-templated text containing origin of the notification.Optional
Asset IPJinja-templated text containing IP to filter notifications.Optional
Asset TypeJinja-templated text containing notification asset type.Optional
Created AfterJinja-templated text containing created after param to fileter notification. Example "2023-10-16T23:59:45.400710Z" or "now-1d"Optional
Created BeforeJinja-templated text containing created beofore param to fileter notification. Example "2023-10-17T23:59:45.400710Z" or "now"Optional
Base TypesJinja-templated text containing comma-separated list basetype used to filter.Optional
SourcesJinja-templated text containing comma-separated list of sources on the notification. Example: source1,source2,source3Optional
StatusStatus of notification. (Default is None)Optional
Is ReadWhether the notification has been read. (Default is No)Optional
Recipient IDJinja-templated text containing ID of user that received the notification.Optional
TagsJinja-templated text containing comma-separated list of tags. Example : tag1,tag2,tag3Optional
LimitJinja templated text containing the limit (Default is 25)Optional
Explode ResultsExplode each result in a separate row. (Default is No)Optional

Output

JSON containing the following items:

{
"result": [{
    "id": "alert-12345",
    "resource": {
      "field1": "value1",
      "field2": "value2"
    },
    "reason": {
      "id": "reason-67890",
      "name": "Critical Alert",
      "text": "This alert was generated due to high CPU usage.",
      "origin": "searches assets"
    },
    "entity": {
      "fieldA": "valueA",
      "fieldB": "valueB"
    },
    "status": "active",
    "generated_at": "2024-11-29T10:15:30Z",
    "created_at": "2024-11-28T14:05:00Z",
    "tags": {
      "tag1": "performance",
      "tag2": "cpu"
    },
    "highlights": {
      "highlight_text": "CPU usage exceeded 90%",
      "data_type": "performance_metric",
      "parent_data_type": "server_metrics"
    },
    "source": "AlertSource",
    "is_read": false
	}],
"error": null,
"has_error":false,
}

Get Notifications

Get a notification by Alert ID.

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Alert IDJinja-templated text containing Alert ID.Required
Recipient IDJinja-templated text containing ID of user that received the notification.Optional

Output

JSON containing the following items:

{
"result": {
  "id": "alert-12345",
  "resource": {
    "field1": "value1",
    "field2": "value2"
  },
  "reason": {
    "id": "reason-67890",
    "name": "Critical Alert",
    "text": "This alert was generated due to high CPU usage.",
    "origin": "searches assets"
  },
  "entity": {
    "fieldA": "valueA",
    "fieldB": "valueB"
  },
  "status": "active",
  "generated_at": "2024-11-29T10:15:30Z",
  "created_at": "2024-11-28T14:05:00Z",
  "tags": {
    "tag1": "performance",
    "tag2": "cpu"
  },
  "highlights": {
    "highlight_text": "CPU usage exceeded 90%",
    "data_type": "performance_metric",
    "parent_data_type": "server_metrics"
  },
  "source": "AlertSource",
  "is_read": false
},
"error": null,
"has_error":false,
}

Release Notes

  • v1.0.0 - initial release with actions - List Notifications and Get Notification

© Devo Technology Inc. All Rights Reserved.