News for hackers. Stuff that matters.
Re:Incident report: Some GOV.UK URLs blocked by deceptive si... by logifail on Tuesday November 29, 2022 @07:09AM (#33786531)
So why is using .govuk.digital for internal services - while still having to purchase and renew the actual govuk.digital domain - preferable to, say, setting everything up under .internal.gov.uk?
Re:Incident report: Some GOV.UK URLs blocked by deceptive si... by dndvr on Tuesday November 29, 2022 @09:17AM (#33787844)
- To reduce the attack surface In the event of site with a *.gov.uk subdomain getting compromised at least it won't now be able to steal auth cookies for internal services

- to keep test/stage as faithful a copy of prod as possible they will have a totally separate but the same DNS set up/CDN set up/ load balancing etc. Theoretically the only difference would need to be one routing rule rather than stuff that might start creating edge case bugs with certs/cookies etc where there are different numbers of segments in domains. Also allows for more certainty/confidence when something is tested in a lower environment that it will work when promoted to prod

Re:Incident report: Some GOV.UK URLs blocked by deceptive si... by kevingadd on Tuesday November 29, 2022 @10:07PM (#33796526)
It's good security practice to have separate sandboxes/domains for various types of services so it's harder for people to pivot from one to another in the event of an exploit. Similar to having a different domain for internal services, if you host user content on your site you should host all that user generated content on a different domain so it can't access your cookies etc.