JupiterOne + WhoIs Integration
Navigate SecOps complexity by connecting Users, Endpoints and Devices with their access to resources in your digital environment by leveraging JupiterOne’s CrowdStrike Integration.
Overview of the WhoIs Integration
By connected users and endpoints with the resources across your entire digital environment via the CrowdStrike Falcon integration, JupiterOne paints a complete picture of the blast radius and scope of potential vulnerabilities.
JupiterOne provides a managed integration with CrowdStrike Falcon. The integration connects directly to CrowdStrike Falcon APIs to obtain configuration about its device sensors/agents.C ustomers authorize access by creating Client API credentials in their CrowdStrike Falcon account and providing those credentials when setting up an instance of the integration in JupiterOne.
WhoIs.net Ingested Resources
The following entity resources are ingested when the integration runs:
| Example Entity Resource | _type : _class of the Entity |
|---|---|
| Account | crowdstrike_account : Account |
| Service | crowdstrike_endpoint_protection : Service |
| Device Sensor Agent | crowdstrike_sensor : HostAgent |
| Prevention Policy | crowdstrike_prevention_policy : ControlPolicy |
Providing Complete Visibility for Leading Cloud-Native Organizations
Providing Complete Visibility for Leading Cloud-Native Organizations
