1.0 Assets

Know what you are protecting

One register of everything your organization runs. Connect AWS, GitHub or your identity provider and it fills itself; add whatever they cannot see by hand.

All assets

Everything this organization owns and has to harden, whether an integration found it or somebody entered it. Systems, processes and data repositories keep their own tabs.

Add asset
Search assets...KindClassificationStatusMore filtersColumns
NameKindOwnerClassificationStatusSourceLast updated
Snowflake ProductionCloud AccountOM. OrtizCriticalActiveManualAug 30
bindsec/cyberwizCode RepositorySR. ShahCriticalActiveGitHubAug 30
cyberwiz-prod-exportsStorage BucketOM. OrtizHighActiveAWSAug 30
cw-siem-sec-01Compute InstanceLA. LevyCriticalActiveAWSAug 30
AWS StagingCloud AccountLA. LevyCriticalActiveAWSAug 30
CW-IPH-017DeviceCD. CohenMediumActiveEA+1Aug 30
cyberwiz-alb-access-logsStorage BucketOM. OrtizMediumDiscoveredAWSAug 30
Azure ProductionCloud AccountNK. NovakCriticalActiveManualAug 29
cw-worker-prod-01Compute InstanceLA. LevyMediumDiscoveredAWSAug 29
github-actionsCode RepositorySR. ShahCriticalDiscoveredGitHubAug 29
CW-DEL-006DeviceCD. CohenLowActiveEntra IDAug 28
legacy-portalCode RepositoryFJ. FischerLowArchivedManualAug 27
  • 1.1

    Found, not remembered

    Integrations report what exists and keep reporting it, so the register stays current between audits instead of being rebuilt before each one.

  • 1.2

    Owners, not orphans

    Every asset carries a named owner, a classification and a status, so a question about it has somewhere to land.

  • 1.3

    Your kinds, your fields

    Five kinds ship with the product. Define your own when they are not enough. New kinds bring their own fields, filters and imports with them.

Provable today, not at audit time.

Run it yourself or have Bindsec run it for you. Either way, the evidence is current and the posture is one place.