Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare crypto/key for release candidate #672

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

vrabotka
Copy link

  • Added features for Key Expiry, Regionality, Replication, Usage Limits, Permissions, Export
  • Added common threat CCC.TH04 and common control CCC.C10

@vrabotka vrabotka requested review from a team as code owners February 20, 2025 04:13
Copy link

linux-foundation-easycla bot commented Feb 20, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

Copy link

netlify bot commented Feb 20, 2025

Deploy Preview for common-cloud-controls canceled.

Name Link
🔨 Latest commit 40d5088
🔍 Latest deploy log https://app.netlify.com/sites/common-cloud-controls/deploys/67b8797a0e890f00081ed1e6

description: |
Supports the ability to assign distinct permission sets to different entities for each key
- id: CCC.KeyMgmt.F28
title: Key Export
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you check whether this feature is allowed in AWS and GCP please?

description: |
Supports the ability to securely replicate a key across different regions
- id: CCC.KeyMgmt.F26
title: Key Usage Limits
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All 3 service providers have different usage limits for keys. But do they allow it to set by the users? Can you provide some references for this capability from AWS, Azure and GCP docs?

- id: CCC.KeyMgmt.F25
title: Key Replication
description: |
Supports the ability to securely replicate a key across different regions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Supports the ability to securely replicate a key across different regions
Supports the ability to securely replicate a key across different regions using automated or manual process.

description: |
Supports the ability to set an expiration date for a key
- id: CCC.KeyMgmt.F24
title: Key Regionality
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a common feature CCC.F22 # Location Lock-In.
Better to have that included under common_features and remove CCC.KeyMgmt.F24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants