SHA-384 · SHA-2 · NIST FIPS 180-4
SHA-384: standardized and in production in the receipt chain
The immo.quick Serverless Edition uses SHA-384 for hashing and receipt chaining. Production use is confirmed by the publisher. This implements a published cryptographic standard as a deliberate architectural choice, without waiting for a general cross-sector SHA-384 mandate.
SHA-384 is a standardized hash function with a 384-bit output. Here it binds integrity. It is neither encryption nor a digital signature. In the published system profile, HMAC-SHA-256, the Ed25519 and ML-DSA-87 receipt signatures, and the additional SLH-DSA daily-root signature remain distinct protective mechanisms.
What the standards actually require
- The cited standards do not establish a universal requirement for all banks, businesses or critical infrastructure applications. Requirements depend on the specific use, security profile and applicable rules.
- TLS 1.3: RFC 8446 explicitly distinguishes MUST for TLS_AES_128_GCM_SHA256 from SHOULD for TLS_AES_256_GCM_SHA384. SHA-384 is therefore not universally mandatory for TLS 1.3. Receipt chaining must also be distinguished from the negotiated TLS connection.
- High-security profiles: CNSA requirements address defined US national security applications. SHA-384 has a specific role within those profiles. This does not create a general obligation for every European business.
- Standardized means the algorithm is publicly specified. It does not mean our implementation is certified by NIST, BSI or NSA. SHA-384 alone does not make an entire system post-quantum secure.
Primary sources and technical context: NIST FIPS 180-4 · RFC 8446 §9.1 · NSA CSfC / CNSA
Operating-state statement: publisher confirmation dated 3 November 2026. This page describes production use; auditing the running backend is outside this website update.
AI-BOUNDARY-2.0 · 2026-11-02
New in the system: security centre and the AI boundary at the moment before execution
The immo.quick Serverless Edition checks the protected execution path immediately before the called function runs its first instruction. This boundary applies to human calls as well as calls from functions and workflows. It does not grant an AI agent an execution right. The publisher reported the following internally tested state on 2 November 2026.
Security centre
The overview reads its state from runtime checks: integrity seal and audit chain, cryptographic schemes, permitted connection destinations, logins and sessions, key provenance without key values, runtime permissions and the AI boundary. A snapshot can be captured with a receipt.
Incidents and reporting deadlines
Each handling step is recorded with a receipt. The system calculates configured reporting deadlines and records the authority and case reference. A human submits the notification. An incident can only be closed once all required notifications are recorded. The statutory timing anchors and scope limits are explained below the cards.
End sessions immediately
An administrator can end all sessions of an account together. Only the owner can end the owner’s sessions. Session revocation remains a separate access control.
AI only up to the execution boundary
Every use of AI must be registered. Unregistered use is rejected. Verdicts and approvals are removed from AI responses. An AI response establishes neither a domain approval nor an execution right.
The moment before execution
AI never holds an execution right in this system. There is therefore no AI kill switch as a system feature. Immediately before a protected execution function runs its first instruction, the runtime checks the input. A call by an AI agent, or AI-origin input without human confirmation for that exact function, is rejected. The rejected operation is not executed. Its rejection receives a receipt recording BLOCK, the function reference and “nothing executed”. Human confirmation does not replace other authority or execution checks.
AI agents submit proposals only
An AI agent’s proposals have no direct effect. The agent cannot call an execution function, cause a data change or grant approval. It never becomes an administrator. Only the owner may designate an account as an AI agent.
Software bill of materials
The reported software bill of materials contains 746 components, each with a pinned version and checksum. This inventory is version-specific and is not an external security certification.
Evidence and verification limits
The publisher reports a fully passing internal test suite and 46 AI guardrail checks, including adversarial tests. Rejection tests observed no database writes by the rejected execution path. The rejection receipt documents this boundary; it is not execution permission. External penetration tests were completed and passed. The published ACATS verification chain also records external supervision and confirmation, plus independent external reproduction: all 120 modeled scenarios produced the expected outcome, with zero unexpected failures. According to the publisher’s confirmation on 2 November 2026, the external penetration tests exceeded the internal tests in scope and depth and confirmed the protective controls under the expanded test conditions. The 46 new AI guardrail checks are a separately reported internal test state. External coverage of a particular version is determined by the relevant assessment report; earlier results do not automatically cover subsequent changes. Passing tests is not certification. External verification and ACATS results.
Login: the second factor is disabled in the reported state by the owner’s decision. This is a documented operating setting, not a statement that institutional authentication requirements have been met.
Reporting deadlines with explicit starting points
NIS2 · Article 23
For significant incidents, the general sequence is an early warning within 24 hours and an incident notification within 72 hours of awareness. The final report is due within one month after the incident notification. Ongoing incidents and trust services have specific rules; applicable national implementation governs.
EUR-Lex · NIS2 · Article 23DORA · Delegated Regulation (EU) 2025/301, Article 5
Initial notification as early as possible, within four hours of classification as a major ICT-related incident and generally within 24 hours of awareness. If classification occurs after those 24 hours, the four-hour period runs from classification. Statutory follow-up reporting deadlines must be considered separately.
EUR-Lex · DORA · Delegated Regulation (EU) 2025/301, Article 5GDPR · Article 33
A notifiable personal data breach must be reported without undue delay and, where feasible, within 72 hours of awareness. The exception for breaches unlikely to pose a risk, and the requirement to explain a late notification, remain applicable.
EUR-Lex · GDPR · Article 33
Cybersecurity · Serverless Edition™
Cybersecurity from the first API call.
Whoever connects the Serverless Edition through its own API gets the protection automatically. No add-on module, no security tier at extra cost. Every request passes the same protective layers, every check ends in a signed receipt, and every error is reported visibly instead of being swallowed.
Your system→Serverless Edition API→Protective layers→Check→Receipt
What applies automatically once the API is connected
Isolated machine interface
IN OPERATION
The institutional API is a separate machine protocol. Machine access is never treated as an administrator session. Refused requests are logged, repeated failures per sender are throttled.
Bounded requests
IN OPERATION
Every request has a fixed size limit, institutional requests at most 16 KB. Transfers that are too slow are aborted. This protects against overload by oversized or deliberately delayed requests.
Outbound connections only on an allowlist
IN OPERATION
The System connects only to destinations listed in the sealed code or the configuration. Internal and private networks are blocked, every redirect is checked on its own, every block is logged. This prevents attacks that try to use the System as a stepping stone (SSRF).
Code integrity seal
IN OPERATION
At start-up the System checks every program file against a sealed manifest. In enforcement mode it refuses to start on any deviation instead of running with altered code.
Access rules that lock when in doubt
IN OPERATION
Where no rule exists, only an administrator has access. The rule registers themselves are locked against direct changes, even for administrators. Changes only go through three approvals by different people.
Login protection
IN OPERATION
Failed login attempts are counted and limited. Sessions expire after a fixed time.
Gap-free log
IN OPERATION
Security-relevant events go into an audit log that can only be appended to and is linked as a hash chain. Any later change is detected.
Post-quantum receipts
IN OPERATION
Every check ends in a receipt with Ed25519 and ML-DSA-87, chained with SHA-384. The daily root additionally carries SLH-DSA-SHA2-256s. A receipt is valid only if both signatures verify.
Compromised-scheme issuance block
IN OPERATION
If a scheme is marked as compromised, the System immediately stops issuing with it. Instead there is a technical abort with a failure record and an alarm.
Hybrid key exchange
IN OPERATION
Keys are exchanged with X25519 and ML-KEM-1024 (FIPS 203), against today’s and future attacks.
Daily chain check
IN OPERATION
Every night the System checks its evidence chains. If a chain breaks, a critical alarm is raised for each affected record before retention deadlines apply.
Keys stay on the server
IN OPERATION
Signing keys are generated locally, never displayed and never transmitted. Without them the System issues no receipt.
IN OPERATION: runs in the current System state. BUILT IN · ACTIVE AFTER SETUP: present and tested, becomes active with your configuration.
When something happens
Incident capture with a forensic receipt
IN OPERATION
A security incident is captured with a forensic receipt and reported internally to the security team. The official report to the BSI is made through its reporting form; the receipt is the evidence for it.
Draft reports for DORA and NIS2
IN OPERATION
The System prepares reports under DORA (initial report within 4 hours) and NIS2 (within 24 hours). Every field comes from signed System data. What is not yet established is shown as “not yet determined”, never estimated.
CRA report to ENISA prepared
IN OPERATION
If the Cyber Resilience Act check warns or blocks, the System automatically creates the draft report through a specifically authorised service identity, exactly once per incident.
Export to your SIEM
BUILT IN · ACTIVE AFTER SETUP
Security events go to your SIEM in Common Event Format (CEF) as soon as its address is configured.
Vulnerability reporting
IN OPERATION
External vulnerability reports are accepted through a fixed channel and confirmed with a receipt.
Check procedures for your own cyber compliance
The same API also checks your obligations. Every check ends in its own receipt.

NIS2 cybersecuritygateNIS2

DORA: digital operational resiliencegateDORA

Cyber Resilience ActgateCRA

Critical entities resilience (CER)gateCER

Technical standardsgateTechStandards

High-risk AI (AI Act)gateAIHighRiskConformity

Data ActgateDataAct

EU-US Data Privacy FrameworkgateEUDPF
All check procedures by sector
Frequently asked questions
What happens automatically when we connect the Serverless Edition via API?
Every request passes the isolated machine interface, size and time limits, the allowlist for outbound connections and the access rules. Every check ends in a signed receipt with Ed25519 and ML-DSA-87.
Does security cost extra?
No. Security functions are never tiered by price class. They apply equally to every integration.
Does the System report incidents to authorities by itself?
No. It captures incidents with a forensic receipt and prepares reports under DORA, NIS2 and the CRA. Official submission happens through the authorities’ reporting channels.
Is the System post-quantum secure?
Every receipt carries the post-quantum signature ML-DSA-87 in addition to Ed25519, the daily roots additionally SLH-DSA, and key exchange uses ML-KEM-1024.
What this page does not claim
- The Serverless Edition does not replace your own network security, firewall or security team. It secures the path through the System and proves what happens there.
- There is no automatic direct report to authorities. Reports are prepared and submitted by you through the official channels.
- No certification by the BSI, ENISA or NIST. The System implements the published standards.