Analyzed data includes all of the security groups protecting EC2 instances and application load balancers (ALBs), from all AWS regions related to the configured access key. AFA separates these instances into groups called security sets. Each AWS security set is a group of instances or ALBs with the same security group and network ACLs, as well as network policies.
The following diagram shows an ASMS Central Manager connecting to an AWS account via HTTPS-REST (TCP/443).
Tip: ASMS also supports connecting to AWS via a proxy server, which can be configured when adding the device to AFA. For more details, see Define a device proxy .
Device access requirements for AWS
ASMS requires the following permissions for your AWS accounts:
Using the standard method: Add an account by providing regular credentials - Access Key ID, Secret Access Key
Using the assume-role method: By using the assumed role method, you can leverage the same authentication credentials for multiple accounts. To implement this, add target AWS accounts to ASMS and configure them to assume the role of an existing AWS base account. During each target account setup, provide the base account's Access Key ID and Secret Access Key and enter the target account's Role ARN.
Note: The setup of target accounts is a sequential process and does not involve simultaneous onboarding of multiple accounts.
Note: The base account does not have to be onboarded to ASMS.
Network Elements Collection Source This read-only field displays the source module that collects the network elements of the subject AWS account and updates the network map.
The default source is AlgoSec Cloud. This means you need to setup the subject AWS account in both Firewall Analyzer AND AlgoSec Cloud. Doing this enables broader support for AWS network elements.
For further details and instructions on how to modify this setting, see "Configuring the AWS Network Elements Collection Source (ASMS A32.10 and above)" in Algopedia.
Proxy
Click Set Proxy Server to configure a proxy server to connect all cloud devices defined in AFA, including both AWS and Azure.
Select the following options for your AWS account as needed:
Real-time change monitoring.Select this option to enable real-time alerting upon configuration changes. For more details, see Configure real-time monitoring.
Set user permissions. Select this option to set user permissions for this device.
Network Elements Collection Source This read-only field displays the source module that collects the network elements of the subject AWS account and updates the network map.
The default source is AlgoSec Cloud. This means you need to setup the subject AWS account in both Firewall Analyzer AND AlgoSec Cloud. Doing this enables broader support for AWS network elements.
Select the following options for your AWS account as needed:
Real-time change monitoring.Select this option to enable real-time alerting upon configuration changes. For more details, see Configure real-time monitoring.
Set user permissions. Select this option to set user permissions for this device.
Enable AlgoSec Cloud to perform AWS data collection and feed the ASMS network map
By default AlgoSec Cloud performs AWS data collection and feeds the ASMS network map using a designated AlgoSec Cloud-ASMS integration. To enable the advantages of this functionality, do the following:
Setup the subject AWS account in both Firewall Analyzer (AFA) AND AlgoSec Cloud. Notes: (1) There MAY be a need to set the 'AWS_Network_Elements_Parse_From_AFA' parameter. Refer to the Algopedia article Configuring the AWS Network Elements Collection Source (ASMS A32.10 and above). (2) The AlgoPedia article Configuring the AWS Network Elements Collection Source (ASMS A32.10 and above) explains the advantages of this workflow, how to continue working in the previous manner if required and how to bring the advantages of this workflow to earlier ASMS versions. (3) When the ASMS-AlgoSec Cloud integration is configured to fetch Routing Data from AlgoSec Cloud, ASMS still connects to AWS to collect the Security Data [Rules, Security Groups, etc.] from AWS.
Microsoft Azure subscriptions in AFA
When you add an Azure subscription to AFA, all VMs related to your subscription are represented in the device tree.
AFA separates the instances into groups called security sets. Each Azure security set is a group of VMs with the same security group and subnet security groups, as well as network policies. VMs with no security groups are assigned to a security set called Unprotected VMs. To enable accurate traffic simulation, AFA automatically creates a rule to allow all traffic for these VMs.
The following diagram shows an ASMS Central Manager connecting to an Azure subscription via HTTPS-REST (TCP/443).
Tip: ASMS also supports connecting to Azure via a proxy server, which can be configured when adding the device to AFA. For more details, see Define a device proxy .
Device requirements for Azure
ASMS requires the following permissions for your Azure subscriptions:
After running a report for an Azure subscription, its topology will be displayed in the network map (with no configuration required).
Options
Select the following options for your AWS account as needed:
Real-time change monitoring.Select this option to enable real-time alerting upon configuration changes. For more details, see Configure real-time monitoring.
Set user permissions. Select this option to set user permissions for this device.