Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Thursday January 26 2023, @09:16PM   Printer-friendly
from the just-wait-and-see-how-long-it-takes-to-migrate-to-IPv8 dept.

NSA offers security guidelines for IPv6 migration:

The US National Security Agency (NSA) has published a guidance document for system administrators to help them mitigate potential security issues as their organizations transition to Internet Protocol version 6 (IPv6).

The prosaically named "IPv6 Security Guidance" [PDF] was compiled for admins inside the Department of Defense (DoD), but is likely to prove useful as a quick reference for anyone managing the transition from IPv4 to IPv6, which could turn out to be a more drawn-out experience than was originally anticipated.

"The Department of Defense will incrementally transition from IPv4 to IPv6 over the next few years and many DoD networks will be dual-stacked," NSA Cybersecurity Technical Director Neal Ziring said in a statement accompanying the publication of the document.

"It's important that DoD system admins use this guidance to identify and mitigate potential security issues as they roll out IPv6 support in their networks."

One of the recommendations is pretty basic: education. Successfully securing an IPv6 network requires, at a minimum, a fundamental knowledge of the differences between the IPv4 and IPv6 protocols and how they operate, the NSA says, so all network administrators should receive proper training.

It advises that security methods used in IPv4 networks will largely also be used with IPv6, but with adaptations to address where there are differences.

Security issues associated with an IPv6 implementation will generally surface in networks that are either new to IPv6 or in early phases of the transition. This is because such networks will lack maturity in IPv6 configuration as well as likely lacking experience in IPv6 by the admins.

Organizations running both IPv4 and IPv6 simultaneously will have additional security risks, with further countermeasures needed to mitigate these due to the increased attack surface of having both IPv4 and IPv6, the document warns.

There are no massive revelations from the NSA, but advice that many admins are likely to be already aware of, such as the recommendation to assign IP addresses on the network via a DHCPv6 server instead of relying on stateless address auto-configuration (SLAAC).

The latter uses a self-assigned IPv6 address that incorporates the fixed MAC address from the NIC, leading to concerns that data traffic could be linked to a specific device and potentially an individual associated with that equipment. Whether this is a major concern to anyone outside of defense or government is another matter, of course.

The NSA also recommends avoiding the use of IPv6 tunneling, often used to transport IPv6 packets within IPv4 packets across existing network infrastructure, again to reduce the potential attack surface and lessen complexity. It advises that tunneling protocols may be allowed if they are required during a transition, but they should be limited to approved systems where their usage is well understood and where they are explicitly configured.


Original Submission

 
This discussion was created by janrinok (52) for logged-in users only, but now has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by janrinok on Friday January 27 2023, @11:06AM

    by janrinok (52) Subscriber Badge on Friday January 27 2023, @11:06AM (#1288893) Journal

    When we think IPv6 is ready then sure more of us will switch over.

    If you think 'being ready' is the same as learning how to do it then you will be waiting for a long time.

    SoylentNews switched over in 2016. My own ISP switched in 2018. I am not aware of any security issues that can be attributed to IPv6 specifically which are not also issues with IPv4 - incorrect configuration being the main common problem. But there are just as many IPv4 mis-configurations as there are IPv6.

    This is because such networks will lack maturity in IPv6 configuration as well as likely lacking experience in IPv6 by the admins.

    Some people won't learn until they are forced to do so but they will eventually have to learn. They won't get any experience by waiting.

    I have 18 different devices on my internal network ranging from desktops, laptops and servers all the way to IoT devices. It is a mix of ethernet and WiFi. They are all IPv6 and they take no more administration than my previous IPv4 network. Every Linux distro that I have used has a perfectly good IPv6 stack.

    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3