Our build principles are all about security and as our founder always like to say, every server is built as an island… Access is the exception, as opposed to the default.
We go out of our way to ensure our servers will maintain its locked down state ongoing.
Updates are important too. It’s easy to ensure they’re uptodate on day 1. Our default build is self-patching (with our watchful eye). We also make sure updates are only ever sourced from reliablle secure repositories.
Unmanaged software would never be installed, unless there’s a compelling reason to do so.
Access is typically granted on a per user basis. Secure passwords are used by default. Having done this for a long time, we’re constanly amazed at the number of insecure passwords we see on servers. Shared logins and weak passwords are the biggest vulnerability.
Documentation comes as standard, which customers can request at any time for free.
Backup routines are created in conjunction with customer conversations.
Dan’s professionalism, knowledge, determination and attention to detail are excellent and I would have no hesitation recruiting him again if the opportunity arose.
Russ Cockburn, IT director, Clearswift
The Dogsbody Linux server build checklist
Dogsbody Technology will:
Build what was agreed at design and advise
Work with customer devs as required
Be on hand for migration and go live (prior arrangement)