microsoft / microsoft/AzureTRE
Key Vault secrets and keys should have an expiration date and capability to rotate
Open
Nobody has claimed this yet.
story
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
A couple more for the list:
- Key Vault secrets should have an expiration date
- Authentication to Linux machines should require SSH keys
Originally posted by @jonnyry in #4303
Description
This issue is a sub-issue of the mentioned reference, to discuss the Security recommendation for having an expiry date for Key Vault secrets and keys. The goal is to discuss and come up with a solution for the secret rotation which satisfies the below acceptance criteria.
Acceptance criteria
- Key vault secrets and keys should have an expiry set
- Secret rotation should be automated with new expiry
- There should be minimum to no downtime during the rotation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced parent issue #4303 and this issue's acceptance criteria; no files or tests are named. Done means Key Vault secrets and keys have expiry dates, rotation is automated with a new expiry, and rotation causes minimal or no downtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100