Linea AureaDocumenta
Security & Compliance

For IT and information security — bundled in one place.

Everything for your IT's initial architecture check in one place: the read-only principle, data flow, system limits and the full 12-point checklist.

Architecture principle

Designed for use in critical-infrastructure environments — not against it.

LAD sits read-only on top of your systems, runs wherever you want it to, and never intervenes in operations. The six points your IT checks first.

In detailThe six principles in detailNo intervention in operations, run where you want, metadata, roles, logging, GDPR.Expand

No intervention in operations

LAD reads and organizes — it does not switch, does not write back, and makes no operational decision. Read-only at operational boundaries.

Runs wherever you want

On-premises in your own data center or in your own cloud. No requirement to use third-party infrastructure — your product data doesn't unintentionally leave your deployment's agreed system boundaries.

Primarily metadata, not bulk data

LAD primarily indexes asset, type, version, deadline and status — document content only where that has been agreed contractually in advance. The source remains the source.

Roles & permissions

Every role sees what it is authorized to see. Access follows your existing permissions concept — no parallel world.

Traceable & consistently logged

Every green light can be traced back to its record, every status and rule change is logged. Verifiable instead of gut feeling.

Built separately, GDPR in view

The public interface and privileged cores are built separately, and data storage is designed for GDPR compliance. Designed for critical infrastructure.

The data flow

How the data flows — and what deliberately stays out.

Your source systems — unchangedSAPELOGISCDEr = 1 · w = 0Read-only adapterLADMetadata indexAsset · type · version · deadline · statusIndex ⊂ sourceControl centerno return channel · no write accessDocument content only by agreement
In detailOne record step by stepSource → access → LAD → view — on a synthetic example, including what deliberately stays behind.Expand
SourceSAP · ELO · GIS · CDE · SharePoint …
→
AccessRead-only connection
→
LADMetadata index
→
ViewControl center

What never leaves the network: The standard case is the metadata layer — asset, record type, deadline, status. Document content is only indexed where that has been agreed contractually in advance. No back-channel into the source systems, no write access at operational boundaries.

What the data flow looks like in a concrete example
SourceSAP PM/EAM · Equipment 10004521, medium voltage · Bay 2
→
AccessRead-only adapter reads equipment & status — maintenance order 45231 stays a reference only
→
LADLinked to asset "Substation South", record type compliance declaration, Gate G4 · Approval
→
ViewControl center: Substation South · 11/12 records · "1 missing"

The same example as in the source systems example and in the document room — SAP remains the source, LAD only reads, changing nothing in the SAP record. All seven examples and the sync status are bundled on the System Connections page.

Limits of the system

What LAD does not decide.

We don't say "trust us" — we show you how to verify it yourself.

LADreadorganiseshowoperational boundaryYour responsible rolesswitchreleaseassessacceptchangeL ∩ E = ∅
  • No switching actionsLAD has no write access to control systems — it reads and organizes, it does not switch anything.
  • No operational approval in place of the responsible personThe control center shows handover readiness — the approval itself remains with the designated role in operations.
  • No automatic legal compliance decisionMaking documentation coverage and deadlines continuously visible does not replace a legal assessment.
  • No acceptance in place of an inspector / expertThe chain of evidence leads back to the record — the technical review remains with your inspectors.
  • No changes to production source systems at operational boundariesRead-only adapters read existing systems, they write nothing back.

In detail with an example chain of evidence (principle → gate → record → document): section "Why you can trust LAD" on the Packages page.

  1. Deployment modelOn-premises in your own data center or in your own cloud — no requirement to use third-party infrastructure.
  2. Network zonesWhich zones and interfaces LAD touches at the operational boundary — and which it explicitly does not.
  3. Authentication / SSO, if availableIntegration with your existing login procedure — project-dependent; nothing is promised here across the board that can't be substantiated.
  4. Roles and permissionsAccess follows your existing permissions concept — each role sees what it is authorized to see.
  5. InterfacesWhich systems are connected via read-only adapters, and what these are explicitly not permitted to do.
  6. Data classesWhat counts as metadata (asset, deadline, status) and what counts as a document — the standard case is the metadata layer.
  7. LoggingEvery change is logged, every statement stays traceable back to its record.
  8. Backup/restoreProcedures and metrics are specified for your specific case, not stated across the board on this website.
  9. Update procedureHow ongoing updates and records logic are rolled out — part of the Control License.
  10. Tenant separationEvery operator works with their own dedicated instance — no shared data storage between operators.
  11. Deletion/retention conceptDefined for your specific case, aligned with your retention obligations.
  12. Exit/uninstallationWhat happens to components, data and configurations upon termination — see FAQ "Contract, Costs & Exit".

Details on SSO, API, encryption, backup metrics or certifications: stated publicly only to the extent they are genuinely verifiable. Security documentation for your specific case is available on request.

Frequently asked

What your IT and information security want to know first.

The most common questions from IT and information security — including audit and compliance. More answers in the FAQ and in the section "Audit, Compliance & Responsibility".

What data does LAD actually read?

Asset and object metadata, document metadata, version and status, deadlines and gates, as well as references to the records. The actual document content is only read if that is intended for your use case and clarified contractually in advance.

Does LAD write data back to our production systems?

No. Read-only at operational boundaries is a principle, not a configuration option — LAD reads and organizes, it does not write back and makes no operational decision.

What logs are generated during operation?

Every status change, rule change and approval is logged traceably with a timestamp and originator — part of the same chain of evidence that also links records to assets. This applies at the business level, not only technical system access. Retention periods, SIEM integration or export formats for your log management are defined in the operator project.

Do our documents leave the network?

As long as LAD only indexes metadata, the document content stays at its place of origin. Certain integrations may also include content — that is then named specifically in advance, not assumed across the board.

What does a security review before the pilot look like?

Architecture discussion → data classification → interfaces → permissions → operating model → approval. The compact checklist for this is above under IT checklist.

Which standards and regulations are on file?

We only publicly name what has been cleared for release. The full, proprietary records catalogs per domain pack are not publicly viewable — they are part of what we jointly configure in the pilot and operator project.

Can LAD map NIS2, KRITIS, EnWG or BSI requirements?

Where within scope, such requirements can be translated into records and governance logic. This is not a certification and not legal advice — the regulatory assessment stays with you.

Questions on the architecture? Let's clarify them directly.

30 minutes, no system access: using your use case we check whether a pilot area can be clearly scoped — no slide deck.

  1. Send a requestBriefly, your topic and your sector.
  2. 30-minute conversationOn your use case, no system access.
  3. A clear answerWhether a pilot area can be clearly scoped.
Request 30-minute Fit Check

Website-specific privacy (cookies, contact form, server logfiles of this website) is covered separately in the Privacy Policy — this page here deals with the architecture and data sovereignty of the LAD product itself. Questions about your specific network and systems we clarify without obligation in a discovery call.