step-security-bot opened a new pull request, #2384:
URL: https://github.com/apache/shiro/pull/2384

   ## Summary
   
   This pull request is created by 
[StepSecurity](https://app.stepsecurity.io/securerepo) at the request of 
@lprimak. Please merge the Pull Request to incorporate the requested changes. 
Please tag @lprimak on your message if you have any questions related to the PR.
   ## Security Fixes
   
   ### Least Privileged GitHub Actions Token Permissions
   
   The GITHUB_TOKEN is an automatically generated secret to make authenticated 
calls to the GitHub API. GitHub recommends setting minimum token permissions 
for the GITHUB_TOKEN.
   
   - [GitHub Security 
Guide](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow)
   - [The Open Source Security Foundation (OpenSSF) Security 
Guide](https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions)
   ### Pinned Dependencies
   
   GitHub Action tags and Docker tags are mutable. This poses a security risk. 
GitHub's Security Hardening guide recommends pinning actions to full length 
commit.
   
   - [GitHub Security 
Guide](https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)
   - [The Open Source Security Foundation (OpenSSF) Security 
Guide](https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies)
   ### Harden Runner
   
   [Harden-Runner](https://github.com/step-security/harden-runner) is an 
open-source security agent for the GitHub-hosted runner to prevent software 
supply chain attacks. It prevents exfiltration of credentials, detects 
tampering of source code during build, and enables running jobs without `sudo` 
access. See how popular open-source projects use Harden-Runner 
[here](https://docs.stepsecurity.io/whos-using-harden-runner).
   
   <details>
   <summary>Harden runner usage</summary>
   
   You can find link to view insights and policy recommendation in the build log
   
   <img 
src="https://github.com/step-security/harden-runner/blob/main/images/buildlog1.png?raw=true";
 width="60%" height="60%">
   
   Please refer to [documentation](https://docs.stepsecurity.io/harden-runner) 
to find more details.
   </details>
   
   ### Add Dependency Review Workflow
   
   The Dependency Review Workflow enforces dependency reviews on your pull 
requests. The action scans for vulnerable versions of dependencies introduced 
by package version changes in pull requests, and warns you about the associated 
security vulnerabilities. This gives you better visibility of what's changing 
in a pull request, and helps prevent vulnerabilities being added to your 
repository.
   
   - [Github Guide about Dependency 
Review](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)
   - [Github Guide for Configuring Dependency Review 
Action](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#using-inline-configuration-to-set-up-the-dependency-review-action)
   ### Maintain Code Quality with Pre-Commit
   
   Pre-commit is a framework for managing and maintaining multi-language 
pre-commit hooks. Hooks can be any scripts, code, or binaries that run at any 
stage of the git workflow. Pre-commit hooks are useful for enforcing code 
quality, code formatting, and detecting security vulnerabilities.
   
   - [Official Pre-commit documentation](https://pre-commit.com/)
   - [Getting Started guide](https://pre-commit.com/#getting-started)
   
   
   ## Feedback
   For bug reports, feature requests, and general feedback; please email 
[email protected]. To create such PRs, please visit 
https://app.stepsecurity.io/securerepo.
   
   
   Signed-off-by: StepSecurity Bot <[email protected]>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to