Step 1: Identify Goals and Use Cases 

Step 2: Determine Data Sources 

Step 3: Deploy Collectors 

Step 4: Connect Data Sources and Integrations 

Step 5: Configure Key Components 

 

Identify data sources required to implement the chosen goal. This is done by Collectors (either Physical or Virtual Collectors) or through integrations which hook into various cloud providers and then pull in data that is used to enrich the picture that the Collector has seen. Integrations include firewalls, switches, WLCs,SIEM/syslog receivers for alerts, and vulnerability scanners.Data sources can be recommended/required per use case type. For example, data sources for use case type Asset Management include Virtual or Physical Collector, Network Mapper, Active Directory, AWS, CrowdStrike, and Tenable. 

 

Integrations  

For information on specific integrations and how to use and deploy them in the Armis platform, go to the Armis Console, Settings, Integrations, and click the “Add Integrations” button on the top right. You will see all of the categorized integrations available: 

 

 

 

 

You can click on the info button for any integration to learn more, or to access the Full Documentation.  

 

 

 

  

Some common integrations include: 

• Amazon Web Services (AWS) 

• Cisco Meraki 

• Google Cloud Platform 

• Lansweeper 

• Microsoft Active Directory 

• SIEM 

• CrowdStrike 

• Azure 

• Intune 

• Rapid7 

• SCCM 

• Tenable 

For more information about setting up integrations, refer to the Integrations page in the User Guide.