Note |
---|
This topic only applies to Armor's private cloud Private Cloud users who are account administrators and new to the Armor Management Portal (AMP). |
...
Complete the onboarding / invitation process
Access AMP
Invite users
Set up your infrastructure
Note |
---|
Before you begin, Armor recommends that you review pre-installation/pre-deployment information, such as virtual machine offerings and supported browsers. To learn more, see Pre-deployment considerations for Armor's private cloudPrivate Cloud. |
Expand | ||
---|---|---|
| ||
|
...
Expand | ||
---|---|---|
| ||
|
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Step 1: Create an IP GroupIn the Firewall screen, each entry in the table represents a single firewall rule; however, each firewall rule can contain several IP addresses or just a single IP address. You can combine related IP addresses into a single IP Group. For example, if you want to block traffic from three separate IP address, you do not have to create three separate firewall rules. Instead, you can combine the three separate IP addresses into a single, configurable IP Group. Then, when you create a firewall rule, you can pick the newly created IP Group as your Source or Destination IP addresses.
Step 2: Create a Service GroupIn the Firewall screen, each entry in the table represents a single firewall rule; however, each firewall rule can contain several protocols (and ports). You can combine related protocols (and ports)into a Service Group. For example, if you want to create a firewall rule to block three types of traffic, you do not have to create three separate firewall rules. Instead, you can combine the three types of traffic (protocols and ports) into a single, configurable Service Group. Then, when you create a firewall rule, you can pick the newly created Service Group.
For a complete list of supported services and sub-protocol, see Review supported services and sub-protocols. Step 3: Create a Firewall Rule
After you create a rule, Armor recommends that you place the rule in the correct order.
|
Expand | ||
---|---|---|
| ||
In the Armor Management Portal (AMP), roles are similar to job titles that you can create and assign to your users. You can populate these roles with certain permissions. For example, you can create an Audit role, and then you can add specific permissions that will give the assigned user permission to access audit-related features. By default, a new administrator account contains an Admin role with all the available permissions selected. When you create a new user account, you must assign that user a role. You can assign a default role or create a new role.
|
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Armor recommends that you configure your account to receive notifications for Account, Billing, and Technical events.
|
Expand | ||
---|---|---|
| ||
An organization allows you to specify when a group of users should be added to a specific support ticket, based on the subject matter of the ticket. For instance, for a billing-related ticket, you can indicate that members of the Billing organization should be notified. When a support ticket is shared with an organization, all users within the organization will receive an initial email notification.
|
...