Private network

Exactly.

Defending against this requires strict network egress filtering, specifically blocking special use IP addresses defined in RFC 6890, RFC 1918, RFC 4193, and RFC 4291.

But the briefing notes that both mechanisms share one specific critical vulnerability, the local host and loopback native client attack vector.

Yes, this is a tough one.

Okay.

The authorization server's security filters check that IP.

It's not an internal RFC 1918 address.

It's not a loopback address.

You see a power supplier, you want to understand what are you allowed to do and not allowed to do and be very judicious.

And the final one, this is the most interesting, was there was a misconfiguration at one customer between the load balancer and the firewall where they weren't properly routing RFC 1918 routes to null.

And so as a result, these requests would start to bounce between the load balancer and the firewall and actually launch.

An internal denial of service.

So either way.

What's a VPN? Virtual Private Network.

Yes.

So I'm in the States.

If you're not good at networks are not good, excuse me, that's a bit short.

If you haven't gone deep on networking, I'm talking to cybersecurity folks today who are like, Oh, now and they confuse that for like RFC 1918 addresses, folks, it's not that right.

I mean, yes, that is a common case for NAT right using network address translation.

But you can masquerade as any IP address, right? In fact, that's how I set up networks.