What we look at
- Which servers, applications, databases and services run, where they run and how they connect. That becomes the inventory.
- The versions of operating system, runtime, database and frameworks. We check them against the vendor end of support dates in our EOL calendar.
- Missing updates, known vulnerabilities, and who has access over SSH or any other way.
- On the host, the open ports, the firewall rules on the server and in the cloud, and the TLS certificates. From these we see who can reach the system from where.
- What you back up, where to, and when someone last tested a restore.
- What the monitoring watches, who gets an alert and which jobs could fail unnoticed.
- Whether runbooks, credentials and dependencies are documented well enough for someone else to run the system.
We check the same layers we also look after: application, runtime and build, data, operating system and host network. We do not look at Windows Server, firewall appliances, workplace IT or .NET Framework.
How we go about it
You give us read only access to the systems in question and, where available, to the source code and existing documentation. With it we read configuration, package versions, logs and jobs. We change nothing on the system itself, and we restart nothing.
What the systems do not tell us, we clear up in a short conversation with you. Ten days after access is in place, you have the report.
What you get
The report is written and ends with an action plan that ranks the findings by risk. For each one it says what needs doing and what happens if nobody does it. Who works through the plan is up to you: us, your own team or another provider.
Finally we propose a service level for your system. It says what we would take on and what that costs per month. We go through the report with you in a meeting.
A sample table of contents:
- Summary and risk assessment
- Inventory: servers, applications, databases, services
- Versions and end of support per component
- Security findings
- Network and firewall on the host
- Backups and restore
- Monitoring and alerting
- Documentation and access
- Action plan by risk
- Service level proposal
- Appendix: vendor sources and raw data
- Inventory
- Versions against end of support
- Security
- Backups and monitoring
- Documentation
Action plan
- highUpgrade the runtime before end of support
- mediumSchedule a restore test
- lowComplete the runbooks
Price
The Legacy Check costs EUR 3,900 plus VAT as a fixed price. That covers up to three Linux servers and one application with its databases. The price includes the report with its action plan, the service level proposal and the meeting where we go through the report with you.
If your system runs on more servers or includes several applications, we quote a separate fixed price beforehand. We always agree the scope in writing before we start.
What comes next
Lobster Legacy Care starts with the Legacy Check. If you then decide on a takeover, we build on the report. For the 24/7 Critical service level we require a completed Legacy Check.