SEC536: Adversarial AI - Penetration Testing AI Systems


Experience SANS training through course previews.
Learn MoreLet us help.
Contact usBecome a member for instant access to our free resources.
Sign UpWe're here to help.
Contact UsIPv6 adoption has progressed unevenly across the industry despite meaningful gains at several large service providers. Much of the hesitation around migrating to IPv6-first networks stems from uncertainty about how maturely operating systems implement the protocol.
This research tested the four most common operating system families, Windows, Linux, macOS, and BSD, for RFC compliance and behavioral differences across a controlled set of IPv6 test cases. Because RFC specifications leave many implementation details to the developer, behavior was expected to diverge, and the testing confirmed that it did.
All four operating systems uniformly implemented core protocol mechanics, but numerous differences among edge cases allowed each system to be uniquely identified from network traffic alone. Several of those differences carried security implications beyond operating system fingerprinting, including divergence in extension header chain limits and potentially non-compliant RFC behaviors. More than 25 years after the first IPv6 specifications were published, implementation-specific behaviors persisted among the most popular IPv6 network stacks, and accounting for them is relevant to any organizations planning an IPv6 deployment.


















