Ministry of Justice sets minimum security standards for AWS

Written by PublicTechnology staff on 17 June 2019 in News
News

Users of S3 storage warned against allowing public access, to tackle ‘leaky bucket’ risk

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 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


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 found that the ministry was responsible for far more breaches of personal data than any other department, recording 3,184 in 2017-18.

Share this page

Tags

Categories

CONTRIBUTIONS FROM READERS

Please login to post a comment or register for a free account.

Related Articles

Government formally unveils annual independent cyber audits for all departments
24 April 2023

Ministerial announcement follows initial examinations of Home Office and business department earlier this year

‘Extremely concerned and disappointed’ – more councils caught up in Capita breach
24 May 2023

Authorities have complained about the lack of time taken to be notified by IT firm and wrongly being told personal data was not put at risk 

Interview: CDDO chief Lee Devlin on the ‘move from being disruptive to collaborative’
23 May 2023

In the first of a series of exclusive interviews, the head of government’s ‘Digital HQ’ talks to PublicTechnology about the Central Digital and Data Office’s work to unlock £8bn...

Government urged to update product safety standards for internet age
15 May 2023

Parliamentary committee laments pace of progress so far in changing rules

Related Sponsored Articles

Proactive defence: A new take on cyber security
16 May 2023

The traditional reactive approach to cybersecurity, which involves responding to attacks after they have occurred, is no longer sufficient. Murielle Gonzalez reports on a webinar looking at...