Frequently Asked Questions
How do I sign up to ARGOS?
What requirements are there for a user to log in?
The following identities are supported by ARGOS:
Azure Active Directory
Azure Key Vaults - Ensure that the expiration date is set on all keys
Azure Key Vaults - Ensure that the expiration date is set on all secrets
Our Azure Storage Accounts are all configured with Firewall settings. Can we still use ARGOS to monitor them?
Yes, you can. This requires some configuration on the Storage Accounts to whitelist the ARGOS service IP on the Storage Accounts. Follow the documentation here and contact our support team to learn about our internet IP.
Onboarding Cloud Environments
Add Azure to ARGOS
ARGOS requires an Azure AD application to authenticate to a customer's Azure cloud. You can create one in a few simple steps:
Add AWS to ARGOS
ARGOS requires an AWS IAM user to authenticate against an organisation's AWS account.
What do I have to deploy to use ARGOS?
Almost nothing. You'll only have to add an Azure Service Principal / Azure AD App Registration (for Azure) or your AWS IAM credentials (for AWS) to ARGOS.
How much does it cost me to run ARGOS?
Where does ARGOS store its data?
The metadata about rule detections is stored in a secured database located in Australia.
Is our data secure?
ARGOS encrypts sensitive data like the Azure or AWS credentials with AES-256 GCM in our database.
What data does ARGOS store?
ARGOS does not store any actual data about your environment apart from metadata like cloud resource IDs. We will never read any files or access any application data in your environment. ARGOS does not store any Personal Identifiable Information (PII) nor credit card information.
What happens to our data after we cancel our subscription?
Customer data is automatically marked for deletion 30 days after the end of the subscription.
Working with ARGOS
Can we ignore resources?
Yes, ARGOS automatically ignores cloud resources with the following tag:
Can we ignore a detection?
Yes, specific detections can be ignored by an ARGOS user if they are expected on a resource.