Summary
baesystems has , and 1 expired in the CertReports index, last verified 2 Nov 2026. The strongest row is EU-US Data Privacy Framework: Inactive. This page is independent of the vendor’s own trust centre: dates, sources and caveats come from CertReports captures.
Reviewer brief
As of 12 Oct 2026, baesystems' EU-US Data Privacy Framework status is listed as Inactive. The DPF registry shows baesystems originally self-certified on 19 Oct 2016, as of 12 Oct 2026. As of 12 Oct 2026, the Data Privacy Framework listing for baesystems is expired with no active renewal recorded. No public evidence found for SOC 2, PCI DSS, or HIPAA compliance for baesystems as of 12 Oct 2026. Based on the evidence as of 12 Oct 2026, the only compliance record for baesystems pertains to the expired EU-US Data Privacy Framework self-certification from 2016.
- EU-US Data Privacy Framework: expired, self-certified 19 Oct 2016, status Inactive as of 12 Oct 2026 (DPF registry).
- SOC 2 Type II: no public evidence found.
- HIPAA BAA / PCI DSS: no public evidence found.
Facts only, each dated; nothing here is inferred, scored or advised. Brief generated 18 Oct 2026; it is regenerated whenever a row changes.
Evidence count
0verified rows
aerospacedefenseengineeringindustrial systems
Compliance grid
Legal artefacts
No DPA, BAA or subprocessor list has been captured from a public page yet. Registry rows above do not depend on this.
Subprocessors
No subprocessor list captured yet.
Change history
- 18 Sep 2026First indexed by CertReports1 evidence row across 1 framework entered the index.
Evidence against regulations
All regulations for baesystemsHow much of each regulation’s vendor requirements baesystems’s public evidence reaches.
Reviewing a vendor on public evidence
All articlesWhat Is Third-Party Risk Management (TPRM)? A Practical Guide
Solomon Amos · 2 Nov 2026 · 10 min read
What Is a Trust Centre? Vendor Evidence vs Office Settings
Solomon Amos · 28 Oct 2026 · 10 min read