Try this first
- 1Inventory endpoints with SSL Labs or testssl.sh. Caveat: SSL Labs only tests publicly reachable endpoints. Internal services (file servers, databases, intranet, IoT) are not covered, inventory those separately with nmap "ssl-enum-ciphers" or testssl.sh against the internal IP range.
- 2Web servers: TLS 1.2 minimum, TLS 1.3 preferred
- 3Database/SMB protocols separately, often forgotten
- 4Legacy system: isolate instead of expose
When to bring us in
Legacy ERP or medical that can't do TLS 1.2, plan replacement.
See also
- I think I clicked a phishing linkNo shame, happens to everyone. The next fifteen minutes matter.
- A colleague's account is acting strangelySending mail in their name, rules hiding folders, unusual sign-ins. Suspicious.
- Lost the MFA app: new phone, no backup codesClassic problem after a phone upgrade. You are not the first to be locked out.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.