View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008976 | 10000-002: Security | Spec | public | 2023-05-22 09:32 | 2024-06-13 17:13 |
Reporter | Barrucand | Assigned To | Paul Hunkar | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | 1.04 | ||||
Fixed in Version | 1.05.04 RC1 | ||||
Summary | 0008976: Security level evaluation of the updated certificates compared to the endpoint should be specified | ||||
Description | The part 2 §7.3.4 v1.04 states that the GDS establishes a secure channel using the highest security level available in the target Server. It does not provide updated CRLs, Certificates or TrustLists via an endpoint that has a lower security level than the security level of the updates. To carry out this it would be necessary to have a clear definition on how 'higher security level" for CRLs, certificates or TrustLists shall be evaluated. We read into this requirement that we should use the security policy of the secure channel since it seems a convenient way to manage it. If we understood this correctly, it seems that the relative weight of security level between security policies would be necessary to evaluate the requirement. Once this data is available we should be able to determine if the provided certificates are compliant for the secure channel security policy or a lower secure policy level. Another interpretation might be to take as reference, one of the certificates used to establish the secure channel. In this case it will be necessary to precise which certificate to choose between client and server certificate as reference for the security level depending on concrete criteria. Moreover it should be precised which certificate properties to take into account and the hierarchy/weight between them. As example, how to estimate the security level between an RSA key of 2048 bits length with SHA512 for signature and an RSA key of 4096 bits length with SHA256 for signature ? As an other example, how to compare RSA and ECC public keys? | ||||
Tags | No tags attached. | ||||
Commit Version | 1.05.04 RC | ||||
Fix Due Date | |||||
related to | 0008938 | closed | Paul Hunkar | Part 4 §6.1.3 should indicate that the error reported by the server to the client is Bad_SecurityChecksFailed for all steps |
|
Added text to check security level of endpoint and to ensure that updates use the same or higher level |
|
Agreed to changes in virtual F2F. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-05-22 09:32 | Barrucand | New Issue | |
2023-05-26 14:57 | Paul Hunkar | Relationship added | related to 0008938 |
2023-06-06 15:22 | Jim Luth | Assigned To | => Paul Hunkar |
2023-06-06 15:22 | Jim Luth | Status | new => assigned |
2024-06-13 17:11 | Paul Hunkar | Status | assigned => resolved |
2024-06-13 17:11 | Paul Hunkar | Resolution | open => fixed |
2024-06-13 17:11 | Paul Hunkar | Fixed in Version | => 1.05.04 RC1 |
2024-06-13 17:11 | Paul Hunkar | Note Added: 0021365 | |
2024-06-13 17:13 | Jim Luth | Status | resolved => closed |
2024-06-13 17:13 | Jim Luth | Commit Version | => 1.05.04 RC |
2024-06-13 17:13 | Jim Luth | Note Added: 0021366 |