Platform

Infrastructure posture

See cloud and code the way a privacy duty sees them: storage left open, identities that can reach personal data, and repositories that leak identifiers. AWS, Azure, GCP, and Kubernetes today. More estates can be added.

Infra posture

Cloud and code

  1. 01
    Estate
    Live

    Cloud accounts

    ProvidersAWS · Azure · GCP
    ClustersKubernetes
  2. 02
    Finding
    Blocked

    Public bucket with identifiers

    ExposurePersonal data reachable
    OwnerStorage account
  3. 03
    Control
    In review

    Reasonable security

    DutySafeguards on personal data
    ActionRestrict public access
  4. 04
    Posture
    Sealed

    Open items 4

    ID: ip-7c21
    15 Oct 2026, 21:04 IST
    Cloud posture summary.

What it does

Cloud accounts

AWS, Azure, and GCP. Findings that put personal data in reach: public storage, open logs, over-broad roles.

Clusters

Kubernetes workloads and attached storage in the same list, not a separate report.

Code repositories

Identifiers committed in the open, and flows that skip a consent or notice check.

One posture list

Open items, owners, and whether the duty is a safeguard, a notice gap, or a rights gap.

More estates can be added

Further clouds and on-prem estates use the same finding list when you add them.

Feeds discovery

A store the posture scan finds can be added to the personal-data inventory. It does not stay a nameless alert.

Under the DPDP Act

  • Reasonable security safeguards. The Act requires safeguards on personal data. An open bucket of identifiers is that duty failing, not a generic “cloud hygiene” item.
  • Breach readiness. Knowing which accounts hold personal data is how a fiduciary answers who was affected. Posture is an input to that list.

Questions

  • Cloud accounts and clusters where personal data may sit: AWS, Azure, GCP, and Kubernetes. Findings are the misconfigurations that make that data reachable, not a generic security score.

  • No. It is the privacy view of the same estate: open storage, over-broad identity, and logs that should not be public. Security teams still own the fix path.

  • Yes. Repositories are checked for identifiers left in the open and for paths that skip a consent check. Findings join the same posture list as cloud items.

Related guides

Next: data discovery on the stores you already run.