"Learn how to quickly populate Guardium groups with data from your own databases and keep those groups in sync with your data. Using Import > From external datasource automates the creation of custom tables, domains, and queries to populate Guardium groups from your own datasources. Once created, these artifacts represent a durable connection between Guardium and your data: updates to your data become reflected in the associated Guardium groups."
Groups are the building blocks that rules and queries reference, for example privileged users, production servers and sensitive objects. Importing members from your own data lets policies reflect the real environment without manual maintenance.
Limits: Run Once Now allows a maximum of 5,000 imported members. A scheduled import has a default maximum of 20,000 members, adjustable with the CLI command store populate_from_query_maxrecs .
Other ways to populate groups: Add members manually in the Members tab, import from a file, or use the populate-from-query GuardAPIs such as populate_group_from_query and run_populate_group_from_query .
After changes: Reinstall the policy. A change in group members affects enforcement only after reinstall.
Why the others are wrong: There is no group-alert feature driven by threat-intelligence feeds, no "group domain with predefined firewall policies," and no synchronization of group domains with internal audit logs.
Submit