Lack of centralized security best practices
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
Hello,
All security related information is scattered across different sections, for example :
I think that it's preferable to create a centralized section that consolidates all security measures,including securing endpoints, exporters, integrations, storage ...
Thanks in advance for your consideration.
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 by reviewing the linked basic auth, security model, TLS encryption, and Alertmanager HTTPS documentation pages to map where security guidance currently lives. Define the scope and structure of a centralized security section, covering the measures named in the issue. Done means the relevant guidance is consolidated without losing coverage or creating conflicting instructions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100