forked from mscurtescu/secevent
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathdraft-scurtescu-secevent-risc-use-cases.txt
280 lines (140 loc) · 7.42 KB
/
draft-scurtescu-secevent-risc-use-cases.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
secevent M. Scurtescu
Internet-Draft Google
Intended status: Informational June 29, 2017
Expires: December 31, 2017
Security Events RISC Use Cases
draft-scurtescu-secevent-risc-use-cases-00
Abstract
This document describes the RISC use cases for security events and
helps with defining the requirements for token format and event
distribution.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 31, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Scurtescu Expires December 31, 2017 [Page 1]
Internet-Draft Security Events RISC Use Cases June 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3.1. Explicit IdP to RP . . . . . . . . . . . . . . . . . . . 2
3.2. Explicit RP to IdP . . . . . . . . . . . . . . . . . . . 3
3.3. Implicit IdP to RP . . . . . . . . . . . . . . . . . . . 3
3.4. Implicit RP to IdP . . . . . . . . . . . . . . . . . . . 4
3.5. Pseudo-implicit . . . . . . . . . . . . . . . . . . . . . 4
3.6. Identity as a Service . . . . . . . . . . . . . . . . . . 4
3.7. Security as a Service . . . . . . . . . . . . . . . . . . 4
3.8. On-Premise RP . . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
2. Definitions
o Transmitter - the entity that sends security events
o Receiver - the entity that receives security events
o IdP - Identity Provider, in most cases but not always this is the
transmitter
o RP - Relying Party, in most cases but not always this is the
receiver
o RISC - Risk and Incident Sharing and Coordination, see
http://openid.net/wg/risc/
o SCIM - System for Cross-domain Identity Management, see
http://www.simplecloud.info/
3. Use Cases
3.1. Explicit IdP to RP
o Transmitter: IdP
o Receiver: RP
Simplest use case, IdPs send security events to relevant RPs.
RP can make control plane calls to the IdP and can authenticate with
access tokens issued by IdP.
Scurtescu Expires December 31, 2017 [Page 2]
Internet-Draft Security Events RISC Use Cases June 2017
3.2. Explicit RP to IdP
o Transmitter: RP
o Receiver: IdP
The RP can also send RISC events back to IdP. We want to make it
very easy for the RP to do that, no complicated registration steps
and crypto of possible.
IdP can document well-known endpoint for data plane (where it
receives events). RP can use access token when sending events on
data plane and maybe does not need to sign SETs.
If RP is sophisticated and is exposing its own control plane then
during RP stream registration with IdP (either manual or
programmatic) it can advertise its own issuer and that issuer through
.well-known can specify full transmitter functionality of RP.
3.3. Implicit IdP to RP
o Transmitter: implicit IdP
o Receiver: implicit RP
Example: Google and Amazon, Amazon account can be backed by gmail
address. Amazon acts as implicit RP to Google in this case.
Google and Amazon need legal agreement, When Amazon account is
created or updated with gmail address Amazon makes REST call to
Google to enroll this new email address for RISC events. If
enrollment succeeds then RISC events will flow bidirectionally (see
next section, for simplicity only unidirectional is considered in
this section).
Assumption: Amazon/RP is registered with Google/IdP as an OAuth 2
client and can use access tokens for control plane.
Open question: what are the implications of unverified email
addresses?
Open question: discovery of hosted domains, how does Google know that
example.com is managed by Oracle and that subject enrollment should
be sent to them?
Scurtescu Expires December 31, 2017 [Page 3]
Internet-Draft Security Events RISC Use Cases June 2017
3.4. Implicit RP to IdP
o Transmitter: implicit RP
o Receiver: implicit IdP
No enrollent call is strictly necessary. The RP can start sending
events to IdP as new identifiers show up.
3.5. Pseudo-implicit
Common email address or phone number used by two different RPs.
Example: Amazon and PayPal, both Amazon and PayPal each have an
account with the same gmail address.
Mutual discovery by exchanging email address hashes.
Open question: legal and privacy implications
3.6. Identity as a Service
Example: Google Firebear, IdaaS manages large number of RPs and
implements RP functionality on their behalf.
IdaaS should be able to manage SET distribution configuration for its
RPs with a given IdP using the credentials already established
between the RP and the IdP. Control plane operation to create/update
stream allows that.
Assumption: IdaaS can impersonate RP at IdP (can obtain access token
on behalf of RP)
3.7. Security as a Service
Similar to IdaaS described in previous estion, but the service
provider has its own set of credentials different from the
credentials and RP is using. The SP cannot impersonate the RP at
IdP. The IdP must define delegation rules and allow the SP to make
requests on behalf of the RP.
3.8. On-Premise RP
The RP (receiver) is behind a firewall and cannot be reached through
HTTP. The only way to deliver events is if the RP periodically polls
an endpoint provided by the transmitter.
Scurtescu Expires December 31, 2017 [Page 4]
Internet-Draft Security Events RISC Use Cases June 2017
Author's Address
Marius Scurtescu
Google
Email: [email protected]
Scurtescu Expires December 31, 2017 [Page 5]