arcus-azure / arcus-azure/arcus.security

Windows Credential Manager as Secret Store Option

Open
#150 4 comments 0 reactions 1 assignee Claimed by @GarthJL1965 View on GitHub
secret-provider secret-store
Dominant language
C#
Stars
38
Forks
12
PR merge metrics
No merged PRs in 30d

Description

**What secret store are you interested in?**

I'm very interested in using the Windows Credential Manager as a Secret Store Provider/Option - I successfully campaigned for this and used it at my last place of work - for C# Win32 Services in particular. I think we need to stipulate, we're talking about Windows XP+ here. A Seperate version could be made available for *nix, Mac 'KeyStores'

**What scenarios would it enable you?**
1) A person who has access to the 'secret' can set it up on the deployment server using the a) standard Windows Credential Manager or b) a Utility with a pop-up GUI - in this situation the roles of developer/installer are divided

2) The Service/Application can have the code to create the required Secret in the Windows Credentials 'Store' built in (much as per (b) from point 1, called at (example) Service installation time - as per (1), the secret need not be made available to the Developer, if roles/responsibilities etc are different (the lines in DevOps, DevSecOps blur some of this now)

**More information**
Because my previous code was 'commercial', I would need to re-do it for this - I'm happy to write & test the code, using C# & Win32 Interop

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.