Skip to main content

Data Handling

This guide explains what Breeze Agent collects, how Breeze-derived data is protected, and how access control and auditing apply in Cloudaware.

Scope of Data Collected​

  • Inventory facts:
    • Hardware: CPU, memory, disks, NICs.
    • OS: name, version, kernel/build, uptime.
    • Filesystems: mount points, size/usage.
    • Software: installed packages and programs.
    • Services: installed/running services and agents.
    • Local accounts: users and groups.
  • Cloud metadata:
    • Cloud account/subscription/project identifiers.
    • Instance/VM IDs, regions/zones, tags/labels.
  • Custom metrics/facts (optional):
    • Application‑specific metrics that you choose to emit via custom collectors or SDKs (see Custom metrics).

By design, collection focuses on configuration and inventory, not on application payloads or log contents.

Data Protection​

  • In transit:
    • All Breeze Agent ↔ Breeze Server traffic is encrypted over HTTPS.
    • Mutual TLS and signature checks protect against man‑in‑the‑middle tampering.
  • At rest:
    • Data stored in Cloudaware is protected by platform‑level encryption at rest (for example, Salesforce/underlying cloud provider controls).
    • Breeze Server logs and configuration data are stored in controlled environments with restricted access.

See the Cloudaware security overview for platform‑wide controls that apply to all modules.

Exclusions and Minimization​

  • Breeze does not intentionally collect:
    • Application payload data.
    • Secrets such as private keys, passwords, or tokens (beyond the agent’s own credentials).
  • Where possible, collected values are limited to identifiers and configuration metadata to minimize PII exposure.
  • If you implement custom metrics or facts, ensure they follow the same principles (no sensitive payloads).

Access Control & Auditing​

  • Access to Breeze‑derived data in CMDB is governed by Cloudaware RBAC (roles, profiles, and sharing settings).
  • Use tags, folders, and scoping rules to:
    • Restrict which teams can see specific environments or business units.
    • Separate production and non‑production visibility.
  • Breeze Server maintains logs of agent communications, which can support security investigations and operational troubleshooting.