Network Security
Policy Object: Application Groups
Table of Contents
Expand All
|
Collapse All
Network Security Docs
-
- Security Policy
-
- Security Profile Groups
- Security Profile: AI Security
- Security Profile: WildFire® Analysis
- Security Profile: Antivirus
- Security Profile: Vulnerability Protection
- Security Profile: Anti-Spyware
- Security Profile: DNS Security
- Security Profile: DoS Protection Profile
- Security Profile: File Blocking
- Security Profile: URL Filtering
- Security Profile: Data Filtering
- Security Profile: Zone Protection
-
- Policy Object: Address Groups
- Policy Object: Regions
- Policy Object: Traffic Objects
- Policy Object: Applications
- Policy Object: Application Groups
- Policy Object: Application Filter
- Policy Object: Services
- Policy Object: Auto-Tag Actions
- Policy Object: Devices
-
- Uses for External Dynamic Lists in Policy
- Formatting Guidelines for an External Dynamic List
- Built-in External Dynamic Lists
- Configure Your Environment to Access an External Dynamic List
- Configure your Environment to Access an External Dynamic List from the EDL Hosting Service
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Policy Object: HIP Objects
- Policy Object: Schedules
- Policy Object: Quarantine Device Lists
- Policy Object: Dynamic User Groups
- Policy Object: Custom Objects
- Policy Object: Log Forwarding
- Policy Object: Authentication
- Policy Object: Decryption Profile
- Policy Object: Packet Broker Profile
-
-
-
- The Quantum Computing Threat
- How RFC 8784 Resists Quantum Computing Threats
- How RFC 9242 and RFC 9370 Resist Quantum Computing Threats
- Support for Post-Quantum Features
- Post-Quantum Migration Planning and Preparation
- Best Practices for Resisting Post-Quantum Attacks
- Learn More About Post-Quantum Security
-
-
-
- Investigate Reasons for Decryption Failure
- Identify Weak Protocols and Cipher Suites
- Troubleshoot Version Errors
- Troubleshoot Unsupported Cipher Suites
- Identify Untrusted CA Certificates
- Repair Incomplete Certificate Chains
- Troubleshoot Pinned Certificates
- Troubleshoot Expired Certificates
- Troubleshoot Revoked Certificates
Policy Object: Application Groups
To simplify the creation of security rules, applications requiring the same
security settings can be combined into an application group.
Where Can I Use This? | What Do I Need? |
---|---|
|
To simplify the creation of security rules, applications requiring the same
security settings can be combined into an application group. An application group is an
object that contains applications that you want to treat similarly in
security rules. Application groups are useful for enabling access to applications that you
explicitly sanction for use within your organization. Grouping sanctioned applications
simplifies the administration of your rulebases. Instead of having to update individual
security rules when there is a change in the applications you support, you can update only
the affected application groups.
When deciding how to group applications, consider how you plan
to enforce access to your sanctioned applications and create an
application group that aligns with each of your policy goals. For
example, you might have some applications that you will only allow
your IT administrators to access, and other applications that you
want to make available for any known user in your organization.
In this case, you would create separate application groups for each
of these policy goals. Although you generally want to enable access to
applications on the default port only, you may want to group applications
that are an exception to this and enforce access to those applications
in a separate rule.
Create an Application Group
Create an Application Group (Strata Cloud Manager)
Group sanctioned applications to simplify administration of your
rulebases.
An application group is an object that contains applications that you want to treat
similarly in policy. Application groups are useful for enabling access to
applications that you explicitly sanction for use within your organization. Grouping
sanctioned applications simplifies the administration of your rulebases. Instead of
having to update individual security rules when there is a change in the applications
you support, you can update only the affected application groups.
When deciding how to group applications, consider how you plan to enforce access to
your sanctioned applications and create an application group that aligns with each
of your policy goals. For example, you might have some applications that you will
only allow your IT administrators to access, and other applications that you want to
make available for any known user in your organization. In this case, you would
create separate application groups for each of these policy goals. Although you
generally want to enable access to applications on the default port only, you may
want to group applications that are an exception to this and enforce access to those
applications in a separate rule.
- Select ManageConfigurationNGFW and Prisma AccessObjectsApplicationApplication Groups and select Add Application Group.
- Give it a descriptive Name and select Add Application Groups.
- Select Add Applications to add the applications you want in the group and then select Save.
- Select Push Config to save your configuration and deploy it to your network.
Create an Application Group (PAN-OS & Panorama)
Group sanctioned applications to simplify administration of your
rulebases.
An application group is an object that contains applications that you want to treat
similarly in policy. Application groups are useful for enabling access to
applications that you explicitly sanction for use within your organization. Grouping
sanctioned applications simplifies the administration of your rulebases. Instead of
having to update individual security rules when there is a change in the applications
you support, you can update only the affected application groups.
When deciding how to group applications, consider how you plan to enforce access to
your sanctioned applications and create an application group that aligns with each
of your policy goals. For example, you might have some applications that you will
only allow your IT administrators to access, and other applications that you want to
make available for any known user in your organization. In this case, you would
create separate application groups for each of these policy goals. Although you
generally want to enable access to applications on the default port only, you may
want to group applications that are an exception to this and enforce access to those
applications in a separate rule.
- Select ObjectsApplication Groups.
- Add a group and give it a descriptive Name.
- (Optional) Select Shared to create the object in a shared location for access as a shared object in Panorama or for use across all virtual systems in a multiple virtual system firewall.
- Add the applications you want in the group and then click OK.
- Commit the configuration.