GOVERNATLAS / PRODUCT DOSSIER

AIShield

AIShield presents AISpectra for model scanning and red teaming and AIGuardian for runtime AI firewall controls.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Choose scanning, red teaming and runtime firewall work separately. The current site’s migration from the earlier Bosch domain establishes a source transition, not an entitlement to every component. Identify the deployment, responsible operator and data path where each selected control applies.

What this record does not establish

The prior Bosch AIShield site directs users to this current domain. Confirm contracting identity, module entitlement and deployment responsibilities; standards mappings are not certification.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

In a proposed authorized sandbox, inspect one synthetic model artifact and one agent workflow. Preserve a scanner observation separately from a runtime permitted/denied action pair. Re-run a case after changing the configured policy, keeping any unsupported model or modality visible.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A current module/deployment/contracting scope record.
Separate artifact-assessment and action-enforcement observations.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

AIShield presents AISpectra for model scanning and red teaming and AIGuardian for runtime AI firewall controls. Scope: primary documentation only; no independent product test or compliance determination.

Source, dates & preserved provenance

AIShield — current primary product documentation ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: eaad6d05cf0ba9f86c7df3af05a232c91b6ecca8d2ef544da92816be3e6694e6

The hash identifies the preserved capture. The live source may have changed.

Source register

AIShield — current primary product documentation ↗vendor owned · captured 2026-10-16

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Can you provide a current module/deployment/contracting scope record for the selected configuration?

Can you provide separate artifact-assessment and action-enforcement observations for the selected configuration?

Which exact version, entitlements, data paths and responsible roles apply?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗