Prisma can be deployed on public or private cloud, off or on-prem. The Prisma agent can be installed for visibility to containers or servers. The agent returns data to the Prisma console. Authentication to a Prisma customer's instance, among other functions, allows retrieval of agent data to asset management systems such as Lansweeper.
Examples of fields that might fit the Lansweeper paradigm of asset management are listed below. There are some that are redundant; this reflects various output formats for different use cases or my error. Some fields are unique to the Prisma environment, but these might be particularly useful in Lansweeper to give context - similar to how "Asset Groups" have been used in Lansweeper.
|
|
|
|
|
|
|
OS: Type and Distribution |
|
|
|
|
|
|
|
|
|
|
|
|
Collections (specific label type used to organize Prisma agent hierarchies, reports, actions, etc.) |
|
|
|
|
|
|
|
|
Compliance Distribution: Critical |
Compliance Distribution: High |
Compliance Distribution: Low |
Compliance Distribution: Medium |
Compliance Distribution: Total |
|
Firewall Protection: Enabled |
Firewall Protection: Supported |
|
|
|
Cloud Metadata: Account ID |
Installed Products: Has Package Manager |
Installed Products: OS Distro |
Vulnerability Distribution: Critical |
Vulnerability Distribution: High |
Vulnerability Distribution: Low |
Vulnerability Distribution: Medium |
Vulnerability Distribution: Total |
|
