FAQ

FAQ will try to help answer the most frequent questions and answers.
If you still have questions feel free to send us a support ticket here if you are an existing customer or contact us from the Contact Us page if you don’t have an account with us.

There is no software to install or agents to setup. We take advantage of native features built into AWS to detect threats to your AWS resources.

No, you don’t have to write one line of code to take full advantage of our platform and its automation features. We have done all the heavy lifting for you with our proprietary rules engine. Our platform comes with a baseline set of rule that you can setup and configure.

Yes, there are video walkthroughs on how to setup permissions and add new accounts for monitoring and automation. Log into your account and you can navigate to “Setup Documentation” at the bottom of the sidebar menu at the very bottom.

Senturion Guardian does not use user credentials such as username\password or Access Keys ID\Secret Access Key to gather threats from your account. We follow the AWS Security Best-Practice of using Cross Account Roles with External ID to Assume a Role in your AWS account. This avoids having to embed credentials as part of account configuration.

Securely Accessing Customer AWS Accounts with Cross-Account IAM Roles

We use a CloudFormation template to allow you to easily setup only the permissions needed to gather various logging data such as CloudTrail, AWS GuardDuty and permissions needed to perform automation task.

At no time does Senturion Guardian ever have access to destroy AWS resources in your account. The role that is setup does not include delete actions on ANY resource in your AWS account.

We gathering all threat finding from AWS GuardDuty. We allow AWS to run your VPC Flow logs, CloudTrail logs and DNS logs through their machine learning models that are part of GuardDuty. We then allow you to setup up rules to reactivate the threats discovered in your AWS Accounts.