mitre / mitre/serverless-inspec-lambda
Explore the Use of Tags to Help Specify the Instances the Scans Need to Run On
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This is a feature/enhancement request.
The need to scan multiple AWS instances at once is fairly common across enterprise settings. AWS Inspector, for example, allows one to configure Assessment Targets based on AWS tags, which makes parallel scanning of multiple instances (or groups of instances that share the same commonalities) a breeze (please see https://docs.aws.amazon.com/inspector/latest/userguide/inspector_applications.html)
It would be wonderful to somehow have the ability to use tags to specify what instances a particular scan should run on.
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
No files, tests, or concrete entry points are named. Start by mapping how the Ruby AWS Lambda wrapper receives scan configuration and invokes InSpec, then inspect how AWS instances are selected. Done would require a defined tag-based target flow that can select multiple instances, but the issue does not specify the configuration or test details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, ruby
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100