←back to thread

I read the federal government’s Zero-Trust Memo so you don’t have to

(www.bastionzero.com)
656 points EthanHeilman | 3 comments | 27 Jan 22 15:06 UTC | HN request time: 0.001s | source
Show context
solatic ◴[27 Jan 22 21:29 UTC] No.30106992[source]▶
Meh. OMB also mandated moving to IPv6 more than a decade ago: https://www.cio.gov/assets/resources/internet-protocol-versi...

Nobody cares. It just gets postponed forever.

replies(1): >>30111727 #
1. AaronFriel ◴[28 Jan 22 07:38 UTC] No.30111727[source]▶
The memo you're linking to was recently updated and did have force. The DOD, one of the largest federal agencies, issued its own memo with similar deadlines, and this & others have had the result of jumpstarting IPv6 / dual stack support for all of the major clouds & Kubernetes.

If FedRAMP qualification is tied to IPv6 support, you'll see every major contractor and cloud provider support it promptly.

If you look at the recent updates for cloud providers - AWS and GCP support for IPv6, Kubernetes going dual stack by default - you can see that this memo had a substantial impact.

Sometimes these things take time, but in this case, the recent memo you link to lit a fire under everyone.

replies(1): >>30113460 #
2. Hikikomori ◴[28 Jan 22 11:45 UTC] No.30113460[source]▶
Yeah AWS has added a lot of ipv6 support recently, like ipv6 only subnets so you can actually benefit from using ipv6. Waiting for rds support though.

Azure is so far behind on this it's silly.

replies(1): >>30123095 #
3. AaronFriel ◴[29 Jan 22 02:11 UTC] No.30123095[source]▶
What doesn't work with IPv6 on Azure? I understood they were first to support it of the major clouds, though maybe it was just in preview support for a long time.

I think in 2019 I was able to use IPv6 VNETs.