SSWConsulting / SSWConsulting/SSW.Rules
Security Debt - Securing Azure Functions
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc: @pierssinclairssw @william-liebenberg @adamcogan
To Myself,
Right now, all of the SSW Rules Azure Functions HTTP endpoints are publicly accessible, which means there is a DoS attack surface and associated costs.
- Investigate how to protect some / all Azure Functions API endpoints
- Investigate what security options should be used (e.g. rate limiting, IP filtering ect.)
Thanks,
-Brady
Contributor guide
No contributing guide indexed for this repository
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 SSW Rules Azure Functions HTTP endpoints and the linked Azure DevOps work item. Investigate protection options such as rate limiting and IP filtering; done means identifying which endpoints should be protected and documenting the recommended security approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100