Discovery · Systems handbook
Systems handbook
Musterwerk Antriebstechnik GmbH
Scope and limits
Customer portal
Every statement carries an evidence label, so you can see what we checked and what remains open.
Purpose and users
- Observed
About 300 customer accounts check order status, delivery dates, and download certificates.
- Observed
Delivery dates shown are from the previous night's sync.
Architecture
- Validated
PHP application with its own database on a rented virtual server.
- Validated
Data arrives as CSV files exported from the ERP at 02:00 and imported at 03:00.
Build and release
- Validated
No build process: files are copied to the server by hand.
- Validated
The running code differs from the agency's repository in 14 files (F6).
Operations
- Observed
No monitoring. Failures are noticed when customers call.
- Validated
Daily server snapshot by the hosting provider; application-level restore never tested.
Known risks
- Validated
End of support for the operating system (F1).
- Validated
Open administrative access (F2) and outdated password storage (F3).
- Validated
Silent sync failures (F4).
Knowledge gaps
- Unverified
Whether any customer integrates with the portal automatically.
- Inferred
The agency's original specification appears to be lost.
Evidence labels
- Observed
- We saw it, or it was shown or told to us directly.
- Validated
- We checked it against code, configuration, logs, or a test.
- Inferred
- A reasoned conclusion from what we saw, not yet checked.
- Unverified
- Reported to us, but we could not confirm it.