ARGUS Client Setup Checklist

Infrastructure and Endpoints

What types of endpoints (servers, workstations, laptops, etc.) does Client have?

How many endpoints does Client plan to monitor with Argus?

What operating systems (Windows, Linux, macOS, etc.) are Client's endpoints running on?

Are Client's endpoints physical or virtual?

Does Client have any containerized environments (e.g., Docker, Kubernetes)?

Network and Connectivity

How do Client’s endpoints connect to the network (wired, wireless, VPN)? If using VPN, please provide details.

What type of network infrastructure does Client have (on-prem, hybrid, cloud-only)?

Does Client have any existing network security controls (firewalls, IDS/IPS, etc.)? If yes, specify if any ports need to be opened for communication.

Applications and Services

Which cloud applications does Client want to monitor (e.g., Office 365, AWS, Google Cloud, GitHub, Docker)?

Does Client have any custom or legacy applications that require special consideration?

Are there any specific compliance or regulatory requirements for application monitoring at Client?

Does Client have existing security solutions (SIEM, SOAR, firewalls, antivirus, IDS/IPS)? If yes, does Client require integration?

Does Client require integration with existing security tools (e.g., Splunk, Elastic, Microsoft Sentinel)?

Security and Compliance

What are Client’s primary security concerns (e.g., threat detection, vulnerability management, compliance)?

Are there any specific security standards or custom policies at Client?

Logging and Data Retention

What are Client’s logging requirements (e.g., log retention period, log storage capacity)?

Does Client have any existing logging solutions or SIEM systems?

Are there any specific data retention or archiving requirements at Client?

How much log data does Client anticipate generating daily?

AWS Specific Questions

In which region are the endpoints located?

Are the endpoints load balanced? If yes, which type?

Are the instances managed by an auto-scaling group?

Are the instances in a public subnet with internet access?

Are there multiple applications running on a single instance?

How is SSL managed?

Apart from EC2, are there any other AWS services used for compute, like Elastic Beanstalk, etc.?

How are secrets and private keys handled?

Is there CI/CD implementation?

Additional Questions

How many employees will potentially use the production environment protected by Argus?

Can you identify 3 to 5 endpoints for the pilot where Argus can install agents?

List down the pilot use cases we will implement during this trial period.

Can we create the Argus AWS instances linked to your AWS organization’s billing account? We will need the account number and other details to link the instances to that billing account.