Discovery · Technical assessment
Technical assessment
Musterwerk Antriebstechnik GmbH
Scope and limits
Summary
6 findings: 3 high, 2 medium, 1 low. Severity reflects the impact on Musterwerk's operations and the likelihood of that impact, given what we could examine.
Findings
F1
Server operating system near end of support
HighValidated- System
- Customer portal
- Finding
- The rented server's operating system loses security updates later this year. Several installed packages are already outdated.
- Evidence
- Validated from the server's package inventory.
- Recommended control
- Move the portal to a supported, managed platform rather than upgrading the server in place.
F2
Administrative access open to the internet
HighValidated- System
- Customer portal
- Finding
- The server's administrative interfaces accept connections from anywhere, protected by password only.
- Evidence
- Validated from the firewall and service configuration.
- Recommended control
- Restrict administrative access to a VPN or named addresses and require a second factor. This can be done in the first week.
F3
Customer passwords stored with an outdated method
HighValidated- System
- Customer portal
- Finding
- Customer account passwords are stored using a method that is no longer considered adequate.
- Evidence
- Validated in the portal code; no customer data was accessed.
- Recommended control
- Migrate to a current password storage method at the next login of each user.
F4
Nightly sync fails silently
MediumValidated- System
- Nightly sync
- Finding
- If one CSV file is incomplete, the whole import stops without notice. Customers then see yesterday's delivery dates. Sales staff report complaints about wrong dates roughly twice a month.
- Evidence
- Validated in the scripts: no error handling or alerting.
- Recommended control
- Replace the file exchange with a small, monitored integration that retries and alerts.
F5
ERP customizations block the upgrade
MediumValidated- System
- ERP
- Finding
- Of about 60 ERP customizations, 9 touch the export used by the sync. These are the main reason the upgrade was postponed.
- Evidence
- Validated from the customization list and the export definitions.
- Recommended control
- Make the new integration use the ERP's standard interface, removing these 9 customizations from the upgrade path.
F6
No record of who changed the portal
LowValidated- System
- Customer portal
- Finding
- Changes have been made directly on the server by the agency and by staff. There is no version history.
- Evidence
- Validated: the running code differs from the agency's repository in 14 files.
- Recommended control
- Put the portal under version control and deploy only through an automated, logged process.