Signal Sciences
Visualize Signal Sciences corps and users, and monitor changes through queries and alerts.
- Installation guide
- Signal Sciences data model
Installation
For this integration, JupiterOne requires a Signal Sciences API Access Token. This can be created by navigating to your user profile within Signal Sciences. See their documentation for additional information on managing API Access Tokens. Once created, save the key to a secure location for use in JupiterOne.
The API Access Token generated on Signal Sciences will inherit the same role as the user that generated it. For this integration, the role of Observer is sufficient for the ingestion of corps and users.
Finalize in JupiterOne
To install the Signal Sciences integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Signal Sciences. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Signal Sciences account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Your Signal Sciences user(the email associated to the Signal Sciences account that created the API access token).
The API access token generated in Signal Sciences for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
CloudWAF | sigsci_cloudwaf | Firewall |
Organization | sigsci_corp | Organization |
User | sigsci_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
sigsci_corp | HAS | sigsci_cloudwaf |
sigsci_corp | HAS | sigsci_user |