Application Group Objects¶
Application group objects provide a way to logically group multiple applications together for use in security policies in Strata Cloud Manager. The scm
CLI provides commands to create, update, delete, show, backup, and load application group objects.
Overview¶
Application groups allow you to:
- Create and manage groups of applications
- Reference both built-in and custom applications
- Use application groups in security rules
- Apply tags for organization
Set Application Group¶
Create or update an application group object.
Syntax¶
Options¶
Option | Description | Required |
---|---|---|
--folder TEXT | Folder for the application group object | Yes* |
--snippet TEXT | Snippet for the application group object | Yes* |
--device TEXT | Device for the application group object | Yes* |
--name TEXT | Name of the application group | Yes |
--members LIST | Comma-separated list of application names | Yes |
--description TEXT | Description of the group | No |
--tag LIST | Tags for categorization | No |
* You must specify exactly one of --folder, --snippet, or --device.
Examples¶
Create a Basic Application Group¶
$ scm set object application-group \
--folder Texas \
--name business-apps \
--members "salesforce,office365,zoom,custom-crm" \
--description "Business critical applications"
---> 100%
Created application group: business-apps in folder Texas
Create an Application Group with Tags¶
$ scm set object application-group \
--folder Texas \
--name collaboration-tools \
--members "slack,ms-teams,zoom,webex" \
--tag "collaboration,approved" \
--description "Approved collaboration applications"
---> 100%
Created application group: collaboration-tools in folder Texas
Delete Application Group¶
Delete an application group object from SCM.
Syntax¶
Options¶
Option | Description | Required |
---|---|---|
--folder TEXT | Folder containing the application group object | Yes* |
--snippet TEXT | Snippet containing the application group object | Yes* |
--device TEXT | Device containing the application group object | Yes* |
--name TEXT | Name of the application group object to delete | Yes |
* You must specify exactly one of --folder, --snippet, or --device.
Example¶
$ scm delete object application-group --folder Texas --name business-apps
---> 100%
Deleted application group: business-apps from folder Texas
Load Application Groups¶
Load multiple application group objects from a YAML file.
Syntax¶
Options¶
Option | Description | Required |
---|---|---|
--file TEXT | Path to YAML file containing application group definitions | Yes |
--folder TEXT | Override folder location for all objects | No |
--snippet TEXT | Override snippet location for all objects | No |
--device TEXT | Override device location for all objects | No |
--dry-run | Preview changes without applying them | No |
YAML File Format¶
---
application_groups:
- name: business-apps
folder: Texas # Container location (folder, snippet, or device)
description: "Business critical applications"
members:
- salesforce
- office365
- zoom
- custom-crm
- name: collaboration-tools
folder: Texas
description: "Approved collaboration applications"
members:
- slack
- ms-teams
- zoom
- webex
tag:
- collaboration
- approved
- name: file-sharing-apps
folder: Texas
description: "File sharing and transfer applications"
members:
- dropbox
- google-drive
- onedrive
- box
tag:
- file-sharing
- name: social-media
folder: Texas
description: "Social media applications"
members:
- facebook
- twitter
- linkedin
- instagram
tag:
- social
- monitor
Examples¶
Load with Original Locations¶
$ scm load object application-group --file app-groups.yml
---> 100%
✓ Loaded application group: business-apps
✓ Loaded application group: collaboration-tools
✓ Loaded application group: file-sharing-apps
✓ Loaded application group: social-media
Successfully loaded 4 out of 4 application groups from 'app-groups.yml'
Load with Folder Override¶
$ scm load object application-group --file app-groups.yml --folder Austin
---> 100%
✓ Loaded application group: business-apps
✓ Loaded application group: collaboration-tools
✓ Loaded application group: file-sharing-apps
✓ Loaded application group: social-media
Successfully loaded 4 out of 4 application groups from 'app-groups.yml'
Note
When using container override options (--folder, --snippet, --device), all application groups will be loaded into the specified container, ignoring the container specified in the YAML file.
Show Application Group¶
Display application group objects.
Syntax¶
Options¶
Option | Description | Required |
---|---|---|
--folder TEXT | Folder containing the application group object | Yes* |
--snippet TEXT | Snippet containing the application group object | Yes* |
--device TEXT | Device containing the application group object | Yes* |
--name TEXT | Name of the application group object to show | No** |
--list | List all application groups in the container | No** |
* You must specify exactly one of --folder, --snippet, or --device. ** If --name is not specified, all items will be listed.
Examples¶
Show Specific Application Group¶
$ scm show object application-group --folder Texas --name business-apps
---> 100%
Application Group: business-apps
Location: Folder 'Texas'
Members: salesforce, office365, zoom, custom-crm
Description: Business critical applications
Tags: None
ID: 123e4567-e89b-12d3-a456-426614174000
List All Application Groups (Default Behavior)¶
$ scm show object application-group --folder Texas
---> 100%
Application Groups in folder 'Texas':
------------------------------------------------------------
Name: business-apps
Location: Folder 'Texas'
Members: salesforce, office365, zoom, custom-crm
Description: Business critical applications
------------------------------------------------------------
Name: collaboration-tools
Location: Folder 'Texas'
Members: slack, ms-teams, zoom, webex
Tags: collaboration, approved
Description: Approved collaboration applications
------------------------------------------------------------
Name: file-sharing-apps
Location: Folder 'Texas'
Members: dropbox, google-drive, onedrive, box
Tags: file-sharing
Description: File sharing and transfer applications
------------------------------------------------------------
Backup Application Groups¶
Backup all application group objects from a specified location to a YAML file.
Syntax¶
Options¶
Option | Description | Required |
---|---|---|
--folder TEXT | Folder to backup application groups from | No* |
--snippet TEXT | Snippet to backup application groups from | No* |
--device TEXT | Device to backup application groups from | No* |
--file TEXT | Output filename (defaults to auto-generated) | No |
* You must specify exactly one of --folder, --snippet, or --device.
Examples¶
Backup from Folder¶
$ scm backup object application-group --folder Texas
---> 100%
Successfully backed up 10 application groups to application-group_folder_texas_20240115_120530.yaml
Backup with Custom Filename¶
$ scm backup object application-group --folder Texas --file texas-app-groups.yaml
---> 100%
Successfully backed up 10 application groups to texas-app-groups.yaml
Best Practices¶
- Logical Grouping: Group applications that serve similar purposes or have similar security requirements
- Naming Convention: Use descriptive names that indicate the group's purpose
- Documentation: Always include descriptions to explain the group's purpose
- Tag Usage: Use tags to categorize groups for easier management
- Regular Review: Periodically review group membership to ensure accuracy
- Use YAML for Bulk Operations: For complex deployments, use YAML files
- Organize by Container: Keep groups organized in appropriate folders, snippets, or devices
Additional Examples¶
Create a Basic Application Group¶
$ scm set object application-group \
--folder Shared \
--name web-apps \
--members "web-browsing,ssl,http,https"
---> 100%
Created application group: web-apps in folder Shared
Create a Comprehensive Business Group¶
$ scm set object application-group \
--folder Shared \
--name critical-business \
--members "salesforce,sap,oracle,custom-erp,custom-crm" \
--tag "critical,business,monitor" \
--description "Critical business applications requiring monitoring"
---> 100%
Created application group: critical-business in folder Shared
Create a Security-Focused Group¶
$ scm set object application-group \
--folder Shared \
--name high-risk-apps \
--members "bittorrent,tor,psiphon,ultrasurf" \
--tag "block,high-risk" \
--description "High-risk applications to block"
---> 100%
Created application group: high-risk-apps in folder Shared
Integration with Security Policies¶
Application groups are commonly used in security rules:
$ scm set security rule \
--folder Shared \
--name "Allow-Business-Apps" \
--source-zones "Trust" \
--destination-zones "Internet" \
--applications "@business-apps" \
--action allow
---> 100%
Created security rule: Allow-Business-Apps in folder Shared
Notes¶
- Application group names must be unique within a container
- Members must be existing applications (built-in or custom)
- Groups can contain both built-in and custom applications
- Tags must exist before being referenced
- Groups are referenced in policies using the "@" prefix
- Empty groups are allowed but not recommended