Skip to content

Security & connection access

Connecting your infrastructure to a compliance tool is an act of trust. Here is exactly what WardBee collects, which permissions it requests, and how you stay in control — in plain language.

Read-only collection

The documented integration setup requests read permissions for collecting configurations and running checks. Scanning does not apply configuration changes. Review the generated policy and avoid granting broader permissions than the connector needs.

Least privilege

Review the permissions of each connection: AWS uses SecurityAudit, ViewOnlyAccess and an explicit Prowler read-only policy; repository connections use scoped read permissions. The Azure preview uses built-in Reader, which allows broader configuration reads than the evidence WardBee collects. GCP is coming soon.

Dedicated, revocable identities

The recommended AWS setup uses a cross-account role with a unique External ID and temporary STS credentials. GitHub and GitLab use dedicated credentials scoped to selected repositories or projects. Stored integration secrets are encrypted with AES-256-GCM and are not returned by integration APIs.

Provable, not just asserted

AWS setup includes reviewable CloudFormation and Terraform. The generated role grants the documented read-only collector and Prowler permissions and requires your unique External ID before WardBee can assume it.

You stay in control

You choose which accounts, regions, and repositories are in scope. Disconnecting removes the integration and its stored secrets. Revoke the provider token or role as well; already-issued temporary credentials and in-flight work can remain valid until expiry or provider-side revocation. Disconnecting is not a promise to erase historical evidence.

Isolated per tenant

Connections are isolated per tenant and enforced server-side — one customer's connection can never be used to read another's account. Provider credentials are stored only for that integration, and authorization is checked again before connection management and sync actions.

Access model by provider

ProviderAvailabilityRuntime accessScopeProvider-side revocation
AWSAvailableCross-account role + External IDAccount and selected regionsDelete role
AzurePreview — activation pendingAzure Lighthouse + built-in Reader; no customer secret keysOne subscription or selected resource groupsRemove the Lighthouse assignment in Azure
GCPComing soonNo credentials requested——
GitHubAvailableGitHub App where configured; fine-grained PAT fallback. Metadata and Administration read; Contents optional. Opt-in Software Delivery additionally requests Deployments read for its approved repository.Selected repositoriesUninstall App or revoke token
GitLabAvailableFine-grained project read permissions; Reporter + read_api fallback. Source reads optional.Selected projectsRevoke token

GitHub App connections verify the installation and issue repository-scoped tokens that expire within one hour. GitHub personal token permissions are confirmed by you because GitHub does not expose the complete grant to WardBee. GitLab token scopes and expiry are checked with the provider. Legacy read_api grants can read more data than WardBee collects; prefer fine-grained project permissions. Source scanning is off until you opt in.

Preview — not generally available

Azure read-only preview

Azure support is prepared for a limited preview. Activation requires provider-side validation before a workspace can connect. The setup uses Azure Lighthouse: your administrator reviews an ARM or Terraform template naming WardBee’s identity and grants Reader on one subscription or selected resource groups. You do not share customer passwords, application secrets or storage keys with WardBee.

What the preview checks
Storage account encryption settings and subscription activity log export configuration. Resource-group-only access leaves subscription log checks unavailable. A configured export does not prove log delivery or retention.
Access boundaries
Reader permits broad resource configuration reads within your approved scope. The collector reads configuration, not blob or file contents, Key Vault secret values or log bodies. It requests no Entra directory consent. Entra MFA enforcement and wider Azure scanner coverage are outside this preview.
Evidence and revocation
Incomplete or unreadable evidence cannot produce a passing result. Disconnecting stops new collection and excludes the connection’s evidence from current checks. Remove the WardBee Lighthouse assignment under Service providers in Azure to revoke the grant; Azure propagation and in-flight requests can delay effective revocation.
Discuss Azure preview access

What is collected and retained

  • — Cloud configuration and repository settings become timestamped evidence snapshots.
  • — Findings, evidence digests, and decision history support reports and later review.
  • — Source scanning is opt-in. Repository scans can inspect selected source code for insecure patterns, exposed credentials, and infrastructure configuration. Access is not limited to Terraform files.
  • — Product workflows accept release information, SBOMs, and supporting evidence you upload.

Explore your framework priorities before connecting anything with the compliance advisor . This self-reported exercise does not inspect your infrastructure or verify controls.

AI provider and data handling

WardBee uses Anthropic Claude through Amazon Bedrock for explanations, remediation suggestions, drafts, and evidence review. Automated checks determine technical results; AI explains results but never changes them. In manual evidence reviews, a passing AI pre-check can support an accepted manual assessment when you select the AI path. That assessment remains labeled AI-checked, not auditor-approved.

What each AI request contains

Manual evidence reviews and file classification
When AI evidence processing is enabled, uploaded file contents can be sent to Bedrock: text and extracted DOCX/XLSX content, PDF documents, and PNG/JPEG images. Requests include filenames and evidence dates; rubric reviews also include the control, your answer, and justification. Classification identifies evidence type and dates; the pre-check evaluates rubric items with citations. Request limits can leave some evidence unreadable, which is reported in the review.
Finding explanations and remediation
The workspace identifier, framework and control or integration type, and the evidence summary or failure context submitted with the request. Remediation context can include finding text and framework guidance.
Policy drafts and custom control mapping
The organization profile and policy type, or the custom control text and target framework you submit.
CRA questionnaire review
Product key, name, scope and classification; questions, answers and explanations; related control identifiers and evidence states; and approved document sections, titles and digests. This request includes document references, not document bodies, raw SBOM files or repository contents.

Manual verification requires activation. Within an enabled workspace, AI evidence processing is on by default. An owner or administrator can turn off “Allow AI processing of evidence” under Manual controls → Verification settings before uploading. This disables file classification, AI pre-checks, and AI review paths for new processing; turning it off does not recall earlier requests. Human review paths remain available.

Free-text inputs are sent as supplied. Do not include secrets, credentials, source code or unnecessary personal data in AI inputs; automatic removal is not guaranteed. Manual verification is configured to use EU Bedrock regions and EU inference profiles. Storage location, model processing, and backups are separate parts of the data flow. Confirm workspace-specific processing and retention requirements with us before submitting restricted data.

Hosting, retention, and subprocessors

Data handling depends on the service and workspace. The NIS2 Supplier Check has its own storage and retention schedule in our privacy policy. For WardBee, request the workspace data-processing details: hosting and backup locations, subprocessors, evidence retention, and deletion arrangements. These details cover cloud hosting, AI, payment, and email services. We do not treat a model-region setting as a guarantee about the location or retention of every copy of your data.

Scan-pack validity is not a data deletion deadline. Disconnecting an integration removes its stored credentials; historical evidence, reports, and decision records are separate. Contact us to agree the retention and deletion requirements for that data.

Request data-handling details

Before granting access

Review the IAM template or token scopes in the connection flow. AWS, GitHub, and GitLab are supported today. Azure preview requires activation and is not generally available; GCP is coming soon. We do not publish an independent ISO 27001 certificate or SOC 2 report for WardBee on this site. Supporting a framework in the product does not certify WardBee or your organization against it.

For data handling and deletion requests, read our privacy policy. To discuss security requirements or report a concern, contact the WardBee team. Do not send credentials or raw sensitive evidence in an initial message.

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.