[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Requirements for IPv6 Firewalls

Subject: Requirements for IPv6 Firewalls
From: joelja at bogus.com (joel jaeggli)
Date: Sat, 19 Apr 2014 07:29:42 -0700
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <CAP-guGUquwcsESnKbe9QKE79NzfSBNsye4Sq4cFgjwr8xLODSw@mail.gmail.com> <CALgc3C6v_u3Xrjf1rQ=u+62ctExOEfYWUsor-DzfamLVv+z+uA@mail.gmail.com> <CAK__Kzs7_tY0HggT7PG2STorHqcV-3BAXHmYF=pia0bPa6YXzg@mail.gmail.com> <CALgc3C7Fi0rhBODH+kc2Vk6pE9s9TAoa303TFftTCN_K4G77kA@mail.gmail.com> <CAP-guGXia-YLnN0LN8FrQnQFC7gRQMbbiGXh=OLK+4cz02p+Rg@mail.gmail.com> <CAFy81rnw-Q7gYb8eSz-0LqH+kRgSS6+vWieMH=AL9Ay-x2KPDg@mail.gmail.com> <CAN3um4xY-jtZ23--yBMy=WfjH1kzhgQ2+2DLn8=MNAcuE-ZdKA@mail.gmail.com> <[email protected]> <CAP-guGVevjt4upAtt9bvbWjmARkL7=_D4L38OuBqSs1J69tLkQ@mail.gmail.com> <[email protected]> <CAP-guGW51yRY_2GPBRw6N_1665Nw9qS+d4Drhhp-eLWjuR1ioA@mail.gmail.com> <[email protected]> <CAP-guGUh1LPE8U6yqKRVQzEHVbiu9c6Sb0Np9kRqQh4fLPDxXA@mail.gmail.com> <[email protected]> <[email protected]>

On 4/18/14, 7:04 PM, Jeff Kell wrote:
> PCI requirement 1.3.8 pretty  much requires RFC1918
> addressing of the computers in scope...

It does not

1.3.8
 Do not disclose private IP addresses and routing
information to unauthorized parties.
Note
: Methods to obscure IP addressing may include, but are
not limited to:
 Network Address Translation (NAT)
 Placing servers containing cardholder data behind proxy
servers/firewalls or content caches,
 Removal or filtering of route advertisements for private
networks that employ registered addressing,
 Internal use of RFC1918 address space instead of
registered addresses.

from version two with further explication

https://www.pcisecuritystandards.org/documents/navigating_dss_v20.pdf

version 3

https://www.pcisecuritystandards.org/documents/PCI_DSS_v3.pdf

>  has anyone hinted at PCI for IPv6?

If by hinted at you mean deployed in pci compliant environments then yes.

> Jeff
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140419/d17bba2b/attachment.bin>

Follow-Ups:
- Requirements for IPv6 Firewalls
  - From: gary.buhrmaster at gmail.com (Gary Buhrmaster)

References:
- Requirements for IPv6 Firewalls
  - From: fernando at gont.com.ar (Fernando Gont)
- Requirements for IPv6 Firewalls
  - From: fernando at gont.com.ar (Fernando Gont)
- Requirements for IPv6 Firewalls
  - From: bill at herrin.us (William Herrin)
- Requirements for IPv6 Firewalls
  - From: eugen at imacandi.net (Eugeniu Patrascu)
- Requirements for IPv6 Firewalls
  - From: george.herbert at gmail.com (George Herbert)
- Requirements for IPv6 Firewalls
  - From: eugen at imacandi.net (Eugeniu Patrascu)
- Requirements for IPv6 Firewalls
  - From: bill at herrin.us (William Herrin)
- Requirements for IPv6 Firewalls
  - From: tmorizot at gmail.com (Timothy Morizot)
- Requirements for IPv6 Firewalls
  - From: eyeronic.design at gmail.com (Mike Hale)
- Requirements for IPv6 Firewalls
  - From: simon at per.reau.lt (Simon Perreault)
- Requirements for IPv6 Firewalls
  - From: bill at herrin.us (William Herrin)
- Requirements for IPv6 Firewalls
  - From: simon at per.reau.lt (Simon Perreault)
- Requirements for IPv6 Firewalls
  - From: bill at herrin.us (William Herrin)
- Requirements for IPv6 Firewalls
  - From: simon at per.reau.lt (Simon Perreault)
- Requirements for IPv6 Firewalls
  - From: bill at herrin.us (William Herrin)
- Requirements for IPv6 Firewalls
  - From: rdobbins at arbor.net (Dobbins, Roland)
- Requirements for IPv6 Firewalls
  - From: jeff-kell at utc.edu (Jeff Kell)

Prev by Date: Requirements for IPv6 Firewalls
Next by Date: Requirements for IPv6 Firewalls
Previous by thread: Requirements for IPv6 Firewalls
Next by thread: Requirements for IPv6 Firewalls
Index(es):
- Date
- Thread