hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 6.3.4 SAML binding for CoAP | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 6.3.4.1 Message encapsulation | When CoAP [15] is used as a transport protocol for assertions described in clause 6.3.3, SAML Attribute Queries, SAML Attribute Statements, and key assertions shall be transported as payload in CoAP messages. The Content-Format option shall be set to "application/xml". SAML messages shall not be compressed or otherwise... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 6.3.4.2 Addressing and intermediaries | The URI to access the SAML endpoint shall conform to IETF RFC 7252 [15], clause 6. CoAP proxies may be present on the path to the SAML endpoint, in which case the Proxy-URI option shall be set to URI of the SAML endpoint. If the SAML endpoint is accessible by HTTP, proxies shall act according to IETF RFC 7252 [15], cla... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 6.3.4.3 Security | SAML messages supported by this binding shall be digitally signed according to SAML [5] using ECDSA with SHA-256, as identified by "http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256". SAML Attribute Statements and key assertions shall be encrypted according to SAML [5], where the encryption algorithm shall be AES as ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7 Attribute Based Access Control layer | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.1 Overview | In the present clause access control using ABKEM is defined in a series of layers that allow bridging the capabilities of large universe ABKEM schemes with various access control methods, in particular standardized access control systems. Each layer can be used in a standalone manner. Layer 1, defined in clause 7.2, is... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2 Base ABKEM access control capabilities ("Layer 1") | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.1 Introduction | The present clause defines capabilities to be supported in ABKEM annotations and access structures for large universe schemes which may have the restriction that attributes are to be used only once. |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.2 Attributes | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.2.1 Syntax for attribute declaration | Attributes shall be declared with type, name, and maximum number of occurrence. Attribute declaration at Layer 1 shall comply with the following ABNF [13] specification: attribute-decl = "define" SP attribute-def "." max-occurence [SP source-datatype] CRLF attribute-def = attribute-type "." attribute-name max-occurence... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.2.2 Attribute types | The following attribute types shall be supported: unsigned integer, boolean, and string. Attribute type shall be declared in uppercase (e.g. BOOL) and may be appended parameters (e.g. UINT(2)). The unsigned integer attribute type shall be defined as UINT(k), where k shall be a strictly positive integer. An attribute de... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.2.3 Syntax for ABKEM universe declaration | An ABKEM universe shall be declared conforming to the following ABFN [13] specification: universe = version SP uni-type SP uni-id SP crypto-params CRLF 1*(attribute-decl) version = 1*(ALPHA / DIGIT) uni-type = "CP-ABKEM" / "KP-ABKEM" uni-id = uni-name "." uni-version uni-name = 1*(ALPHA / DIGIT) uni-version = 1*(ALPHA ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.2.4 Syntax for value assignment in annotations | An annotation operation shall provide a reference to the ABKEM universe according to the following ABNF [13] specification: universe-ref = "universe:" SP uni-id CRLF An assignment operation for an attribute of type boolean shall conform to the following ABNF [13] specification: assignment = "set:" SP attribute-type-boo... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3 Policies | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.1 General definition of a policy and syntax | A policy is a logical statement. A logical statement can itself be made of: • a relational statement; or • a logical operation between two logical statements; or • a logical threshold gate between two or more logical statements. A policy shall comply with the following ABNF [13] definition: policy = policy-id SP policy... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.2 Relational statements | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.2.1 Introduction | A relational statement is a comparison between an attribute and a constant by means of a relational operator, in accordance with the type of the attribute. |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.2.2 Relational operators for the unsigned integer attribute type | The following relational operators shall be supported, where A shall be of type UINT(k), k a strictly positive integer, and b shall be a constant of the same type. Table 7.1: Relational operators for unsigned integers Operator Relational statement Matches if < A < b A is strictly inferior to b <= A <= b A is inferior o... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.2.3 Relational operators for the boolean attribute type | The following operators shall be supported, where A shall be of type BOOL: Table 7.2: Relational operators for booleans Operator Relational statement Matches if is_true A is_true A is set to the value 1 is_false A is_false A is set to the value 0 A relational statement for a boolean attribute shall comply with the foll... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.2.4 Relational operators for the string attribute type | The equality operator shall be supported, where A shall be of type STRING and b shall be a string constant: Table 7.3: Relational operators for strings Operator Relational statement Matches if eq A eq b The string represented by A is the same, character-by-character, as the string constant b. A relational statement for... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.3 Logical operators | The following logical operators shall be supported, where X and Y shall be two logical statements: Table 7.4: Logical operators for logical statements Operator Policy statement Matches if AND X AND Y Both X and Y match OR X OR Y Either X matches, Y matches or both A logical operator shall comply with the following ABNF... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.3.5 Top-level statements | A relational statement, logical statement, or threshold gate shall be referred to as a top-level statement when it is evaluated for all branches of the policy, i.e. when it is always evaluated. |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4 ABKEM bindings | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.1 Introduction | This clause specifies the translation rules between Layer 1 access control and the underlying ABKEM implementation. |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.2 Binding rules for value assignment to attributes in annotation | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.2.1 Common translation rules | An ABKEM attribute is an anonymous string. Any attribute defined at Layer 1 shall be translated into an ABKEM attribute set of cardinality max-occurence as defined in the related Layer 1 declaration (refer to clause 7.2.2.1). ABKEM attributes related to the same Layer 1 attribute shall have their identifier defined acc... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.2.2 Unsigned integer | In addition to being subject of the rules in clause 7.2.4.2.1, unsigned integer attributes are decomposed into a set of ABKEM attributes with each ABKEM attribute representing a bit in the base 2 representation of the Layer 1 attribute value. Unsigned integer attributes shall be translated according to the algorithm be... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.2.3 Boolean | Boolean attributes shall be translated according to the algorithm below. Fetch the value of the max-occurence element that corresponds to the declaration of the attribute. For each value of the element id between 1 and max-occurence, annotate with an attribute according to the following ABNF [13] specification, where t... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.2.4 String | String attributes with values assigned using the plain string method shall be translated according to the algorithm below. Fetch the value of the max-occurence element that corresponds to the declaration of the attribute. For each value of the element id between 1 and max-occurence, annotate with an attribute according... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.3 Binding rules for policy translation | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.3.1 Common translation rules | When the ABKEM in use does not support attribute repetition in a policy, implementations translating Layer 1 policies into ABKEM policies shall maintain an occurrence counter for each Layer 1 attribute in the context of a given policy. At the first occurrence of a Layer 1 attribute in said Layer 1 policy, the related o... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.3.2 Integer | 7.2.4.3.2.1 "<" operator A relational statement conformant to the following ABNF [13] specification: "(" attribute-name SP "<" SP uint-constant ")" where the value of the uint-constant element is strictly positive, shall first be translated into a statement in the form: "(" attribute-name SP "<=" SP uint-constant ")" w... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.3.3 Boolean | Let count be the current occurrence counter value of the Layer 1 attribute of type boolean. A Layer 1 relational statement conformant to the following ABNF specification: layerone-rl = "(" attribute-name SP "is_true" ")" shall be translated into the ABKEM relational statement: abkem-rl = "(" attribute-type-bool "." att... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.2.4.3.4 String | Let count be the current occurrence counter value of the Layer 1 attribute of type string. A Layer 1 relational statement conformant to the following ABNF specification: layerone-rl = "(" attribute-name SP "eq" SP string-constant ")" shall be translated into the ABKEM relational statement: abkem-rl = "(" attribute-type... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3 Intermediate access control layer ("Layer 2") | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.1 Introduction (informative) | The present clause describes translation rules allowing to build advanced attributes and policies on top of the access control capabilities supported by a compliant ABKEM scheme, that are specified in clause 7.2. |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2 Additional attribute types | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.1 Double | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.1.1 Definition | The attribute type double shall be used to handle the float and double types as defined in ANSI/IEEE 754TM-1985 [14]. It shall be defined as DOUBLE(k,l), where k and l shall both be strictly positive integers. The declaration shall follow the following ABNF specification: double-decl = "define" SP double-type "." (attr... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.1.2 Relational operators for doubles | Let attr be of type double and const be a constant of the same type. When the operator op is <, >, <=, >=, or !=, the relational statement (attr op const) at Layer 2 shall be translated into a Layer 1 relational statement as follow: ( (attr-ipart op const-ipart) OR ( (attr-ipart == const-ipart) AND (attr-fpart op const... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.2 Time measurement | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.2.1 Timestamp | 7.3.2.2.1.1 Definition The attribute type timestamp allows the representation of elapsed time from an origin. It shall be defined as TIMESTAMP(k, U, C), where k shall be a strictly positive integer, U and C shall be optional string labels. If C is specified, then U shall be specified. Thus, the following constructs sha... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.2.2 Duration | 7.3.2.2.2.1 Definition The attribute type duration in the present clause shall be used to handle the type duration defined in ISO/IEC 8601 [11], over a single measurement unit. It shall be defined as DURATION(k,U), where k shall be a strictly positive integer and U shall be an optional string label. The following const... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.2.3 Cycles | 7.3.2.2.3.1 Definition The attribute type cycles shall be defined as CYCLES(k, C), where k shall be a strictly positive integer and C shall be a string label. The declaration shall follow the following ABNF [13] specification: cycles-decl = "define" SP cycles-type "." (attribute-name) "." max-occurence [SP source-datat... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3 Location | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.1 Zone | 7.3.2.3.1.1 Definition The attribute type zone allows the representation of a location with a pre-configured vocabulary (e.g. countries, regions, districts, building names, floor numbers, room numbers, area numbers, and so forth). It shall be defined as ZONE(n), where n shall be a strictly positive integer. An attribut... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.2 Grid | 7.3.2.3.2.1 Definition The attribute type grid allows the representation of a location as an area made of the intersection of a column and a row. It shall be defined as GRID(n, m, C), where n and m shall be strictly positive integers, and C shall be a string label. The declaration shall follow the following ABNF [13] s... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.3 1d point | 7.3.2.3.3.1 Definition The attribute type 1d point allows the representation of a location on a line as a distance from an origin (e.g. altitude, depth). It shall be defined as 1D-POINT(k, U, C), where k shall be a strictly positive integer, U and C shall be mandatory string labels. The declaration shall follow the fol... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.4 2d point | 7.3.2.3.4.1 Definition The attribute type 2d point allows the representation of a location in a two-dimensional cartesian system. It shall be defined as 2D-POINT(k,l,U,C), where k and l shall be strictly positive integers, U and C shall be mandatory string labels. The declaration shall follow the following ABNF [13] sp... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.5 3d point | 7.3.2.3.5.1 Definition The attribute type 3d point allows the representation of a location in a three-dimensional cartesian system. It shall be defined as 3D-POINT(k,l,m,U,C), where k, l, and m shall be strictly positive integers, U and C shall be mandatory string labels. The declaration shall follow the following ABNF... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.6 Circle perimeter | 7.3.2.3.6.1 Definition The attribute type circle perimeter allows the representation of a location as a distance from a single point of reference within a plane (the circle centre). It shall be defined as CIRCLE(k, U, C), where k shall be a strictly positive integer, U and C shall be mandatory string labels. The declar... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.3.7 Sphere surface | 7.3.2.3.7.1 Definition The attribute type sphere surface allows the representation of a location as a distance from a single point of reference within a volume (the sphere centre). It shall be defined as SPHERE(k, U, C), where k shall be a strictly positive integer, U and C shall be mandatory string labels. The declara... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4 Abstract string types | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.1 Free string | 7.3.2.4.1.1 Definition The attribute type free string allows the representation of a foreign data type, when such foreign data type can be translated into the base STRING type at Layer 1 (refer to clause 7.2). Implementations can keep track of the foreign data type thanks to the source-datatype component. It shall be d... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.2 Clearance | 7.3.2.4.2.1 Definition The attribute type clearance allows the representation of a clearance level. It shall be defined at Layer 2 as CLEARANCE and shall take no parameter, but may be assigned a list of allowed clearance levels (pre-configured strings). The declaration shall follow the following ABNF [13] specification... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.3 Role | 7.3.2.4.3.1 Definition The attribute type role allows the representation of a role. It shall be defined at Layer 2 as ROLE and shall take no parameter, but may be assigned a list of allowed role names (pre-configured strings). The declaration shall follow the following ABNF [13] specification: role-decl = "define" SP r... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.4 User | 7.3.2.4.4.1 Definition The attribute type user allows the representation of a user. It shall be defined at Layer 2 as USER and shall take no parameter. The declaration shall follow the following ABNF [13] specification: user-decl = "define" SP user-type "." (attribute-name) "." max-occurence [SP source-datatype] CRLF u... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.5 Device | 7.3.2.4.5.1 Definition The attribute type device allows the representation of a device. It shall be defined at Layer 2 as DEVICE and shall take no parameter. The declaration shall follow the following ABNF [13] specification: device-decl = "define" SP device-type "." (attribute-name) "." max-occurence [SP source-dataty... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.6 Function | 7.3.2.4.6.1 Definition The attribute type function allows the representation of an executable function. It shall be defined at Layer 2 as FUNCTION and shall take no parameter. The declaration shall follow the following ABNF [13] specification: function-decl = "define" SP function-type "." (attribute-name) "." max-occur... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.7 Datatype | 7.3.2.4.7.1 Definition The attribute type datatype allows the representation of a data type. It shall be defined at Layer 2 as DATATYPE and shall take no parameter. The declaration shall follow the following ABNF [13] specification: datatype-decl = "define" SP datatype-type "." (attribute-name) "." max-occurence [SP so... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.2.4.8 Origin | 7.3.2.4.8.1 Definition The attribute type origin allows the representation of the origin (source) of data. It shall be defined at Layer 2 as ORIGIN and shall take no parameter. The declaration shall follow the following ABNF [13] specification: origin-decl = "define" SP origin-type "." (attribute-name) "." max-occurenc... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3 Support for foreign data types | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3.1 Introduction | The present clause provides rules for supporting foreign data types using those defined at Layer 2 (clause 7.2) and Layer 3 (clause 7.3). |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3.2 Datatypes identified in annex C | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3.2.1 Primitive data types from XML Schema | The string data type from XML Schema [8] shall be translated into a Layer 1 STRING data type, the source-datatype component shall be set to "http://www.w3.org/2001/XMLSchema#string". The boolean data type from XML Schema [8] shall be translated as a Layer 1 BOOL data type, the source-datatype component shall be set to ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3.2.2 Time data types from XML Schema | The time data type from XML Schema [8] shall be translated into a Layer 2 TIMESTAMP data type, the source- datatype component shall be set to "http://www.w3.org/2001/XMLSchema#time". The date data type from XML Schema [8] shall be translated into a Layer 2 TIMESTAMP data type, the source- datatype component shall be se... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.3.3.2.3 Resource identifiers | The X.500 directory name data type shall be translated into a Layer 2 FREESTRING data type, the source-datatype component shall be set to "urn:oasis:names:tc:xacml:1.0:data-type:x500Name". The IETF RFC 822 [i.29] name data type shall be translated into a Layer 2 FREESTRING data type, the source- datatype component shal... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4 ABKEM operations | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.1 General | The present clause specifies methods to implement common access control use cases using Layer 1 (clause 7.2) and Layer 2 (clause 7.3) capabilities. Attribute and constant names are informative and given for consistency of the methods. Implementations shall select appropriate attribute and constant names in order to gua... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.2 Time-based implicit secret key revocation | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.2.1 Implementation in KP-ABKEM | Time-based implicit revocation relies on the ciphertext being annotated with a timestamp attribute with a value of relevance (e.g. the time at which the protected data was captured), and the secret keys being valid for a limited range of value of said attribute by means of a policy evaluating the attribute against boun... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.2.2 Implementation in CP-ABKEM | Time-based implicit revocation relies on the secret key being annotated with one or two timestamp attributes set to boundary constants, and the ciphertext containing a policy based on a comparison against a generated timestamp of relevance (e.g. the time at which the protected data was captured). Let two attributes att... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.3 Counter-based implicit secret key revocation | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.3.1 Implementation in KP-ABKEM | The approach is similar to that described in clause 7.4.2.1, with the timestamp being replaced by an unsigned integer representing a strictly increasing counter. Let an attribute attr be of Layer 1 type UINT(k) with k a strictly positive integer as defined in clause 7.2.2.2. Let constants validity_max and validity_min ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.3.2 Implementation in CP-ABKEM | The approach is similar to that described in clause 7.4.2.2, with the timestamps being replaced by unsigned integers representing strictly increasing counters. Let two attributes attr1 and attr2 be of Layer 1 type UINT(k) with k a strictly positive integer as defined in clause 7.2.2.2. Let constant validity_max , valid... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.4 Simple Mandatory access control | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.4.1 Implementation in KP-ABKEM | Mandatory access control relies on the ciphertext being annotated with an ABKEM string attribute representing a target clearance level, and the secret key being valid for said value by means of a policy that is always comparing the attribute against a string constant. Let an attribute attr be of Layer 2 type clearance ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.4.2 Implementation in CP-ABKEM | Mandatory access control relies on the secret key being annotated with a string attribute representing an assigned clearance level, and the ciphertext being valid for said value by means of a policy that is always comparing the attribute against a string constant. Let an attribute attr be of Layer 2 type clearance as d... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.5 Role-based access control | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.5.1 Implementation in KP-ABKEM | Role-based access control relies on the ciphertext being annotated with an ABKEM string attribute representing a target role set by the encapsulating party, and the secret key being valid for said value by means of a relational statement that compares the attribute against a string constant. If the role is applicable t... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.5.2 Implementation in CP-ABKEM | Role-based access control relies on the secret key being annotated with an ABKEM string attribute representing an assigned role, and the ciphertext being valid for said value by means of a relational statement that compares the attribute against a string constant. If the role is applicable to all branches of the policy... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.6 Location-based access control (informative) | Location-based access control can be implemented using the attribute types and related operators defined in clause 7.3.2.3 using methods similar to those of other ABKEM operations defined in clause 4. Tables 7.13 and 7.14 provide implementation examples for KP-ABKEM and CP-ABKEM. A location restriction set as a top-lev... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.7 Reduced access control based on the emergency level | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.7.1 Implementation in KP-ABKEM | Reduction of access control criteria in case of emergency relies on the ciphertext being annotated with an ABKEM string attribute representing an emergency level set by the encapsulating party, and the secret key holding one or more logical statements allowing access with reduced or no other criteria, when said attribu... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.7.2 Implementation in CP-ABKEM | Reduction of access control criteria in case of emergency relies on the secret key being annotated with an ABKEM string attribute representing the emergency level for which the secret key holder is allowed to bypass normal access control policies for the data protected in the ciphertext (when said emergency level is ap... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.8 Access control based on service tier | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.8.1 Implementation in KP-ABKEM | Access control based on the service tier relies on the ciphertext being annotated with an ABKEM string attribute representing an applicable service tier set by the encapsulating party, and the secret key being valid for said value by means of a relational statement that compares the attribute against a string constant.... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.4.8.2 Implementation in CP-ABKEM | Access control based on the service tier relies on the secret key being annotated with an ABKEM string attribute representing a service tier available to the key owner, and the ciphertext being valid for said value by means of a relational statement that compares the attribute against a string constant. If the service ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5 Translation rules for XACML | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.1 Introduction (informative) | The rules provided in the present clause are applicable to access control systems implementing the XACML Role Based Access Control Profile [7]. Two types of <PolicySet> elements in said profile are of interest for the present clause: • the Role <PolicySet> element which associates a role with a Permission <PolicySet>; ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.2 General requirements | The requirements in [7] shall be supported. In addition, the following additional requirements shall be supported. ETSI ETSI TS 103 532 V1.2.1 (2021-05) 81 In order to allow full compatibility between the XACML-based access control system and the ABE access control system, the expressiveness of XACML elements shall be ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.3 Implementation in KP-ABKEM | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.3.1 KP-ABKEM specific requirements | A ciphertext shall be annotated with attributes representing the characteristics of the data, and may be annotated with contextual attributes. When issuing an access control policy, ABE authorities shall use attributes representing the characteristics of the data for the translation of the <Rule>'s <Target>, and shall ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.3.2 Issuance of secret keys | When issuing ABE secret keys to an access control subject, the ABE Authority shall, in this order: 1) identify the roles that apply to the access control subject; 2) for each role identified in the previous step, retrieve the Role <PolicySet> for which the <Target> element makes the Role <PolicySet> applicable to said ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.3.3 Processing of Permission <PolicySet> element | When an ABE authority has identified a Permission <PolicySet>, it shall: 1) retrieve the tree of <PolicySet>, <Policy> and <Rule> elements by recursively following the <PolicySet>, <Policy> and <PolicySetIdReference> elements, starting from the Permission <PolicySet>; 2) from the tree constructed in step 1, identify al... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.4 Implementation in CP-ABKEM | |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.4.1 CP-ABKEM specific requirements | The ABE authority shall convert polices expressed in XACML into Layer 2 policies when configuring the ABE cryptosystem, such that devices can be provisioned with Layer 2 policies prior to ciphertext being generated. Prior to converting policies expressed in XACML into Layer 2 policies, the ABE authority shall identify ... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.4.2 Preparation of policies for ciphertexts | When preparing Layer 2 policies for ABE ciphertext, the ABE Authority shall, in this order: 1) identify all the roles that are defined in the XACML-based access control system; 2) for each role identified in the previous step, retrieve the Role <PolicySet> for which the <Target> element makes the Role <PolicySet> appli... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.4.3 Processing of Permission <PolicySet> element | When an ABE authority has identified a Permission <PolicySet>, it shall: 1) from the Permission <PolicySet>, retrieve the tree of <PolicySet>, <Policy> and <Rule> elements by recursively following the <PolicySet>, <Policy> and <PolicySetIdReference> elements, starting from the Permission <PolicySet>; 2) for each encryp... |
ba35a078486de8cdd1a51b965fdc9f0e | 103 532 | 7.5.4.4 Encapsulation into ciphertext | Upon encapsulating a data set into an ABE ciphertext, the encapsulating party shall identify the characteristics of the data set and select the corresponding logical statement from the database generated according to clause 7.5.4.2. The logical statement shall be used to produce the ciphertext access structure. ETSI ET... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.