-
Notifications
You must be signed in to change notification settings - Fork 1
/
opsawg-cira-securehomegateway-mud-00.txt
280 lines (168 loc) · 7.97 KB
/
opsawg-cira-securehomegateway-mud-00.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
6tisch Working Group M. Richardson
Internet-Draft Sandelman Software Works
Intended status: Informational J. Latour
Expires: March 21, 2019 CIRA Labs
F. Khan
Twelve Dot Systems
September 17, 2018
MUD processing and extensions for Secure Home Gateway Project
draft-richardson-opsawg-securehomegateway-mud-00
Abstract
This document details the mechanism used by the CIRA Secure Home
Gateway and CIRA MUD integration server to return MUD artifacts to
participating gateway systems.
The work in [I-D.ietf-opsawg-mud] creates a relationship between a
device's manufacturer and a border gateway that may need to enforce
policy. This document ads an additional relationship to a service
provider, trusted by the border gateway to enhance or modify the
stated security policy.
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 March 21, 2019.
Copyright Notice
Copyright (c) 2018 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
Richardson, et al. Expires March 21, 2019 [Page 1]
Internet-Draft SHG-MUD September 2018
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
4. MUD file extensions . . . . . . . . . . . . . . . . . . . . . 3
4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
4.2. YANG FILE . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The initial extension from this document is to provide for a way to
mark a set of ACLs as being enabled even though the device has
quaranteed. {EDNOTE: more motivational text here}
The second issue addressed by the document is the question of whether
and when the MUD file should be specific to a specific version of the
device firmware.
The third issue is that an intermediary (ISP, or third-party security
service) may want to extend or amend a MUD file received from a
manufacturer. In order to maintain an audit trail of changes, a way
to encode the previous MUD URL and signature file (and status) is
provided.
2. Terminology
The major new term, compared to the MUD document is the term
quaranteed: a device which has shown behaviour forbidden by a MUD
file ACL, and has subsequently been denied further access to the
network.
Richardson, et al. Expires March 21, 2019 [Page 2]
Internet-Draft SHG-MUD September 2018
3. Requirements Language
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
[RFC2119] and indicate requirement levels for compliant STuPiD
implementations.
4. MUD file extensions
4.1. Tree Diagram
module: cira-shg-mud
augment /m:mud:
+--rw quaranteed-device-policy
+--rw access-lists
+--rw access-list* [name]
+--rw name -> /acl:acls/acl/name
4.2. YANG FILE
<CODE BEGINS> file "[email protected]"
module cira-shg-mud {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-shg-mud";
prefix "shg";
import ietf-mud {
prefix m;
description "This module defines the format for a MUD description";
reference "RFC YYYY: MUD YANG";
}
organization "CIRALabs Secure Home Gateway project.";
contact
"WG Web: <http://securehomegateway.ca/>
WG List: <mailto:[email protected]>
Author: Michael Richardson
<mailto:[email protected]>";
description
"This module extends the RFCXXXX MUD format to include two
facilities: definition of an Access Control List appropriate
to enable device upgrade only, and provide for a history of
Richardson, et al. Expires March 21, 2019 [Page 3]
Internet-Draft SHG-MUD September 2018
modifications by third-parties to the MUD file";
revision "2017-12-11" {
description
"Initial version";
reference
"RFC XXXX: MUD profile for Secure Home Gateway Project";
}
augment "/m:mud" {
description
"Adds leaf nodes appropriate MUD usage in the
Secure Home Gateway";
container quaranteed-device-policy {
description
"The policies that should be enforced on traffic
coming from the device when it is under quaranteen.
These policies are usually a subset of operational policies
and are intended to permit firmware updates only.
They are intended to keep the device safe (and the network safe
from the device) when the device is suspected of being
out-of-date, but still considered sufficiently intact to be
able to do a firmware update";
uses m:access-lists;
}
}
}
<CODE ENDS>
5. Security Considerations
TBD.
6. IANA Considerations
TBD.
7. Acknowledgements
This work was supported by the Canadian Internet Registration
Authority (cira.ca).
Richardson, et al. Expires March 21, 2019 [Page 4]
Internet-Draft SHG-MUD September 2018
8. Normative References
[I-D.ietf-opsawg-mud]
Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage
Description Specification", draft-ietf-opsawg-mud-25 (work
in progress), June 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>.
Authors' Addresses
Michael Richardson
Sandelman Software Works
Email: [email protected]
Jacques Latour
CIRA Labs
Email: [email protected]
Faud Khan
Twelve Dot Systems
Email: [email protected]
Richardson, et al. Expires March 21, 2019 [Page 5]