8
11/07/2003 IETF-58 MSEC and AAA page 1 George Gross, IdentAware Security [email protected] IETF-58, Minneapolis, MN November 10 th 2003 Multicast Security with Authentication, Authorization, and Accounting (AAA)

11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security [email protected] IETF-58, Minneapolis, MN November 10 th 2003 Multicast

Embed Size (px)

Citation preview

Page 1: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 1

George Gross, IdentAware™ Security [email protected]

IETF-58, Minneapolis, MN

November 10th 2003

Multicast Security withAuthentication, Authorization,

and Accounting (AAA)

Page 2: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 2

What motivates MSEC/AAA?

• Large-scale secure multicast groups straddle administrative/business domain boundaries

• AAA enforces contractual relationships, generates data usable for service accounting

• Allows Service Provider to securely control their multicast transit routing service

• Enables dynamic MSEC groups with the Service Provider AAA as the broker

Page 3: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 3

Relevant Background Reading

• RFC3588, Diameter base protocol spec

• RFC2904, generic authorization framework

• NASREQ Diameter application– ietf-draft-aaa-diameter-nasreq-13.txt

• next rev of generic policy token draft– msec-gspt-04.txt– missed the ID cut-off

Page 4: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 4

GDOI Roaming Pull AAA ModelAdministrative Domain “B”

Group Owner Zauthorization

AuthenticationServer

DiameterAAA Server

Grp. ControllerKey Server

AccountingServer

GMGM

GMGM

DiameterAAA Server

SubordinateGC/KS

AccountingServer

GMGM GM

Administrative Domain “A”

Diameter Diameter

GDOI GDOI

DiameterNASREQ+MSEC

Secure multicastgroup“Z”

Page 5: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 5

Observations about GDOI/AAA

• Can leverage existing IKE/ISAKMP AAA– Q: does the group member have a NAI? – Reasonable design: extend NASREQ Diameter

application to handle GDOI

• Undefined how to add a S-GC/KS to group

• Issue: currently no way to separate KS from the S-GC role if the S-GC domain is not trusted with the group’s encryption key

Page 6: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 6

GSAKMP Push AAA ModelAdministrative Domain “B”

Group Owner Zauthorization

CertificateAuthority

DiameterAAA Server

Grp. ControllerKey Server

AccountingServer

GMGM

GMGM

DiameterAAA Server

SubordinateGC/KS

AccountingServer

GMGM GM

Administrative Domain “A”

Diameter Diameter

GSAKMPGSAKMP

Diameteraccounting

Secure multicastgroup“Z”

Policy token

Page 7: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 7

GSAKMP/AAA Observations

• PKI based authentication only, no NAI

• Multicast policy token encodes membership authorization, acts as AAA service ticket

• Diameter back-end used for accounting

• Does not fit Diameter NASREQ model

• Like GDOI, can not withhold group key from S-GC in partially trusted domain

Page 8: 11/07/2003IETF-58 MSEC and AAA page 1 George Gross, IdentAware ™ Security gmgross@IdentAware.com IETF-58, Minneapolis, MN November 10 th 2003 Multicast

11/07/2003 IETF-58 MSEC and AAApage 8

Future MSEC/AAA directions

• Need to separate the S-GC and key server roles in both GSAKMP and GDOI

• Introduce “generic” policy token attributes to encode multiple service authorizations – nesting the tokens will avoid layer violations– multicast PT is scalable, but it is not part of

GDOI today, is this feasible to add?

• Long-term: Diameter extensions for MSEC