Add cloud devices

Relevant for: AFA Administrators

This topic describes how to add an AWS account or an Azure subscription to AFA, to be managed and analyzed similarly to on-premises devices. ASMS supports Google Cloud Project policy visibility and risks for Google Cloud firewalls added in AlgoSec Cloud.

Add AWS (Amazon Web Service) accounts in AFA

Add an AWS account to AFA to analyze data using the AWS access key ID you provide.

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.

For details, see:

• Network connection
• Permission requirements for AWS
• Add an AWS account to AFA
• Enable AlgoSec Cloud to perform AWS data collection and feed the ASMS network map

Network connection

The following diagram shows an ASMS Central Manager connecting to an AWS account via HTTPS-REST (TCP/443).

Permission requirements for AWS

ASMS requires the following permissions for your AWS accounts:

Device analysis

AFA requires minimal read-only access permissions to access AWS and collect data.

This includes the following AWS access keys:

• Access Key ID
• Secret Access Key

We recommend creating a specific IAM user with access keys instead of relying on root user access keys.

The AmazonEC2ReadOnlyAccess policy must be attached to the IAM user.

For example:

This enables the following permissions for ASMS to perform data collection for target AWS accounts:

Required IAM permission*	API permission	Purpose	ASMS functionality
*Click for link to Amazon API Docs
Access level:  READ
ec2:Describe*	describeInstances	Gets all of the AWS data needed for ASMS	Devices tree, network map & TSQ
	describeVpcs		Devices tree, network map & TSQ
	describeSecurityGroups		Policy visibility, TSQ
	describeNetworkAcls		Policy visibility, TSQ
	describeNetworkInterfaces		Network map & TSQ
	describeInternetGateways		VPN support in network map & TSQ
	describeRouteTables		Network map & TSQ
	describeRegions		Devices tree
	describeSubnets		Network map & TSQ
	describeVpnGateways		VPN support in network map & TSQ
	describeVpcPeeringConnections		Network map & TSQ
	describeVpnConnections		VPN support in network map & TSQ
elasticloadbalancing:Describe*	describeLoadBalancers	Gets the specified load balancers or all load balancers	Network map & TSQ

ActiveChange

When ActiveChange is enabled, the IAM user must have read-only permissions, plus the following additional permissions:

#	Required IAM permission*	API permission	Purpose	ASMS functionality
	*Click for link to Amazon API Docs
	Access level:  WRITE
1	ec2:AuthorizeSecurityGroupIngress	AuthorizeSecurityGroupIngress	Adds the specified inbound (ingress) rules to a security group	Active change
2	ec2:RevokeSecurityGroupEgress	RevokeSecurityGroupEgress	Removes the specified outbound (egress) rules from the specified security group	Active change
3	ec2:RevokeSecurityGroupIngress	RevokeSecurityGroupIngress	Removes the specified inbound (ingress) rules from a security group	Active change
4	ec2:AuthorizeSecurityGroupEgress	AuthorizeSecurityGroupEgress	Adds the specified outbound (egress) rules to a security group for use with a VPC	Active change

For example:

Add an AWS account to AFA

You can add an AWS account to ASMS in two ways:

• 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.

Do the following:

1. Access the DEVICES SETUP page. For details, see Access the DEVICES SETUP page.

2. Click New > Devices.

3. In the vendor and device selection page, select Amazon > Web Services (AWS) EC2.

4. Configure the fields and options as needed:

   

   AWS account fields and options using the standard method

   Access Information	The device type is automatically defined. In the Name field, enter the name that you want to appear in the device tree for this account. Tip: Use the account's host or route name.
   Additional Information	Enter the following details to define access to your AWS account: AWS Access Key ID. Enter your access key, supplied by Amazon. AWS Secret Key ID. Enter your secret key, supplied by Amazon. Regions. Select a region. For example: All China (Beijing) GovCloud Tip: If you want to create a custom list of regions that AFA collects data from, see Set Up Specific Regions for Data Collection in AFA.
   Route Collection	Select one of the following to determine how AFA should acquire the device's routing data. Automatic. Automatically generate routing data upon analysis or monitoring. Static Routing Table (URT). Take the device's routing data from a static file that you provide. For details, see Specify routing data manually. 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. For more details, see Define a proxy server .
   ActiveChange	Select Enable ActiveChange for this device. For details, see Implement changes with ActiveChange.
   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.

   AWS account fields and options using the assume-role method

   Access Information	The device type is automatically defined. In the Name field, enter the name that you want to appear in the device tree for this account. Tip: For example, AWS_Assume_Role
   Additional Information	Enter the following details: Provide the credentials of an existing AWS account: AWS Access Key ID. Enter the access key, supplied by Amazon. AWS Secret Key ID. Enter the secret key, supplied by Amazon. Specify the Region of the new, target account, you wish to onboard to AFA: All China (Beijing) GovCloud Tip: If you want to create a custom list of regions that AFA collects data from, see Set Up Specific Regions for Data Collection in AFA. Assume Role for a Different Account. Select to add a target account that assumes the role of the existing AWS account accessed above. Add the Target Account Role ARN (add the Amazon Resource Name (ARN) of the role to assume.) TIP: Get the Target Account Role ARN in AWS: 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. To change Network Elements Collection Source change the setting of the relevant parameter. See AWS_Network_Elements_Parse_From_AFA. 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 .
   Route Collection	Select one of the following to determine how AFA should acquire the device's routing data. Automatic. Automatically generate routing data upon analysis or monitoring. Static Routing Table (URT). Take the device's routing data from a static file that you provide. For details, see Specify routing data manually.
   Proxy	Click Set Proxy Server to configure a proxy server to connect all cloud devices defined in AFA, including both AWS and Azure. For more details, see Define a proxy server .
   ActiveChange	Select Enable ActiveChange for this device. For details, see Implement changes with ActiveChange.
   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.

5. Click Finish. The new device is added to the device tree.

6. If you selected Set user permissions, the Edit users dialog box appears.

   In the list of users displayed, select one or more users to provide access to reports for this account.

   1. To select multiple users, press the CTRL button while selecting.

   2. Click OK to close the dialog.

A success message appears to confirm that the subscription is added.

In the device tree, AWS subscriptions are shown in three levels: the user account, region/VPC, and security set.

For example:

/bin/algosec_conf --verify-proxy-configuration

Bulk Update of AWS Account Credentials

An API facilitates access/key password updating, which some customers require to do periodically for their AWS accounts, without reloading the accounts, which can be very time-consuming. See Bulk update keys of AWS cloud accounts

Set Up Specific Regions for Data Collection in AFA

When onboarding new accounts, AFA connects to multiple data centers spread across multiple geographical locations (regions) to gather data from the available AWS resources. If you want to limit data collection to specific regions only, this section explains how you can configure a customized set of regions for data collection on the DEVICES SETUP.

Do the following:

1. Edit the file /usr/share/fa/data/plugins/aws/brand_config.xml as follows:

   1. In the configuration file, locate the FORM_FIELD with the title "Regions".

      

      The FORM_FIELD is followed by a list of dropdown options.

   2. Add a new option to the dropdown specifying the regions to collect data from. Set 'value' to the specific data collection regions and 'display' to how the selection appears in the Regions dropdown. For example:

      <OPTIONS value="eu-north-1 eu-central-1 us-east-1 eu-west-1" display="My Regions"/>

2. Save the file.

   Note: For the new option to appear in the dropdown, log out and then log in.

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:

1. Integrate AlgoSec Cloud and ASMS. See ASMS Integration.

2. 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.].

Add 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 VMs into groups called security sets. Each Azure security set is a group of VMs with the same network security group and subnet network security groups.

• VMs with no network 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.

• A Network security group, that is not attached to any VMs or subnets, is placed into a dedicated security set.

For more details, see:

• Network connection
• Permission requirements for Azure
• Add a Microsoft Azure subscription to AFA
• Enable AlgoSec Cloud - ASMS integration (optional)

Network connection

The following diagram shows an ASMS Central Manager connecting to an Azure subscription via HTTPS-REST (TCP/443).

Permission requirements for Azure

ASMS requires the following permissions for your Azure subscriptions:

Device analysis

AFA requires minimal Reader access permissions defined for the subscription to access Azure and collect data.

In your Azure subscription, configure an Active Directory Application to use to connect to AFA.

For details, see How to configure a Microsoft Azure Active Directory application in AlgoPedia.

For example:

The IAM permissions should be Reader.

For example:

#	Required IAM permission*	Purpose	ASMS functionality
	*Click for link to Microsoft API Docs
	Access level:  READ
1	Microsoft.Network/networkSecurityGroups/read	Gets all network security groups in a subscription	Policy visibility, TSQ, and AFF
2	Microsoft.Network/virtualNetworks/read	Gets all virtual networks in a subscription	Devices tree, network map, TSQ, and AFF
3	Microsoft.Network/networkInterfaces/read	Gets all network interfaces in a subscription	Network map, TSQ, and AFF
4	Microsoft.Network/publicIPAddresses/read	Gets all the public IP addresses in a subscription	Topology, network map, TSQ, and AFF
5	Microsoft.Compute/virtualMachines/read	Lists all of the virtual machines in the specified subscription	Devices tree
6	Microsoft.Network/routeTables/read	Gets all the route tables in the specified subscription	TSQ and AFF
7	Microsoft.Network/virtualNetworkGateways/read	Gets all virtual network gateways in the specified subscription	VPN support in network map, TSQ, and AFF
8	Microsoft.Network/localnetworkgateways/read	Gets all local network gateways in the specified subscription	VPN support in network map, TSQ, and AFF
9	Microsoft.Network/connections/read	Gets all the virtual network gateways connections in the specified subscription	VPN support in network map, TSQ, and AFF
10	Microsoft.Web/hostingEnvironments/read	Gets all app service environments for a subscription	Devices tree
11	Microsoft.Network/locations/serviceTags/read	Gets a list of service tag information resources	Content of the network objects in the policy, TSQ, and AFF
12	Microsoft.Network/locations/serviceTagDetails/read	Gets a list of service tag information resources	Content of the network objects in the policy, TSQ, and AFF

ActiveChange

When ActiveChange is enabled, the IAM user permissions must be updated to Contributor.

For example:

Required IAM permission*	Purpose	ASMS functionality
*Click for link to Microsoft API Docs
Access level:  WRITE
Microsoft.Network/networkSecurityGroups/write (create-or-update) Microsoft.Network/networkSecurityGroups/write (delete)	Creates or updates a network security group in the specified resource group	NSG Active change

Add a Microsoft Azure subscription to AFA

Do the following:

1. In your Azure subscription, configure an Active Directory Application to use to connect to AFA if not done already.

   For details, see How to configure a Microsoft Azure Active Directory application in AlgoPedia .

2. In AFA, access the Devices Setup page. For details, see Access the DEVICES SETUP page.

3. In the vendor and device selection page, select Microsoft > Azure.

4. Configure the fields and options as needed.

   Azure subscription field and options

   Access Information	Enter the following details: Name. The Azure subscription's host name or IP address. Subscription ID. The Azure subscription's ID. Tenant ID. The Active Directory Application tenant ID. For more details, see Azure documentation . Application ID. The application client ID. Key. The application key.
   Route Collection	Select one of the following to determine how AFA should acquire the device's routing data. Automatic. Automatically generate routing data upon analysis or monitoring. Static Routing Table (URT). Take the device's routing data from a static file that you provide. For details, see Specify routing data manually.
   Proxy	Click Set Proxy Server to configure a proxy server to connect all cloud devices defined in AFA, including both AWS and Azure. For more details, see Define a proxy server .
   ActiveChange	Select Enable ActiveChange for this device. To learn about Active Change, see Implement changes with ActiveChange.
   Mapping	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.

5. Click Finish.

   The subscription is added to the device tree.

6. If you selected Set user permissions, the Edit users dialog box appears.

   In the list of users displayed, select one or more users to provide access to reports for this account.

   1. To select multiple users, press the CTRL button while selecting.

   2. Click OK to close the dialog.

A success message appears to confirm that the account is added.

/bin/algosec_conf --verify-proxy-configuration

Enable AlgoSec Cloud - ASMS integration (optional)

Enable AlgoSec Cloud-ASMS integration to see:

• VNets and NSGs on the network map.

• Azure Firewalls and Hubs in the device tree and on the network map

To enable AlgoSec Cloud-ASMS integration:

Do the following:

1. Onboard the subject Azure subscription in both AFA AND AlgoSec Cloud.
   

2. Integrate AlgoSec Cloud and ASMS. See ASMS Integration.

3. Enable real time device monitoring. See Configure real-time monitoring. All Azure elements will be visible after the next monitoring cycle.

Device tree display of Azure Firewall

• Azure Firewall: in the device tree, Azure Firewall has a three-tier hierarchy:

  

  1. Subscription (customer-given name for the subscription when onboarded to AFA)

  2. Region/VNet or Virtual Hub

  3. Azure Firewall

• For unassigned Azure Firewall policies (policies which are not assigned to any Azure Firewall): The device tree displays the following three-tier hierarchy:

  Note: Unassigned Azure Firewall policies are not shown in the network map and the TSQ results

  

  1. Subscription (customer-given name for the subscription when onboarded to AFA)

  2. Region/"Unassigned_Firewall_Policies"

  3. Unassigned Firewall Policies

Google Cloud projects in AFA

ASMS supports Google Cloud Project policy visibility and risks for Google Cloud added in AlgoSec Cloud.

To open the Google Cloud Risk Report in AlgoSec Cloud from ASMS.

Do the following:

1. In the ASMS device tree, select the Google Cloud Project.

2. Click the link to Google Cloud Risk Report to open the report in AlgoSec Cloud.