The Ministry of Justice has published security guidelines for its more than 120 Amazon Web Services (AWS) cloud computing accounts, designed to provide a “lowest common denominator” for security settings.

“We wanted to set the baseline at a good level, while catering for diverse architectures and applications, without creating unreasonable high-effort tasks for teams but ensuring we avoid common bad practice missteps,” according to newly published blogpost [1] from senior security engineer Siddharthan Elangovan and Joel Samuel, a cybersecurity consultant working with the ministry.

They identified “S3 leaky bucket” as a common problem, referring to AWS’s Simple Storage Service (S3) which provides ‘buckets’ of online space for files, from which many organisations have suffered leaks due to poor configuration. The baseline bars users for making S3 buckets ‘world’ – meaning publicly – readable unless this is the specific intention. Usage is monitored centrally and the ministry will automatically remove ‘world’ access after a warning. Similar requirements are in place for AWS Compute services.

Related content

• Which government department suffers the most data breaches? [2]
• Report reveals massive spike in Home Office data breach reporting following GDPR [3]
• Government commits £500m to defence innovation scheme [4]

The baseline requirements also insist on use of GuardDuty, CloudTrail and Config, AWS’s threat detection, user tracking and configuration auditing services, on all accounts at all times. They also require all AWS objects to be tagged for ownership.

Users are banned from using resources outside the EU, and the service’s Identity and Access Management service must be used, with alerts when new accounts are created and idle ones suspended. When encryption is offered by AWS for a service, it must be enabled.

Elangovan and Samuel said that further security may be appropriate in some cases. “The baseline is our current minimum security posture for our MOJ AWS accounts – not what we think is a gold standard,” they wrote. “This helps set a bar but gives teams latitude for doing things differently when they need to.”

Research for PublicTechnology published in May [2] found that the ministry was responsible for far more breaches of personal data than any other department, recording 3,184 in 2017-18.