> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/projects/security-posture.md).

# Security Posture

### What is Security Posture?

Security posture is calculated by running a set of checks on the source code of each component.

This includes direct and transitive dependencies.

List of Security Posture Checks

* Branch Protection: Are the default and release branches protected with GitHub's branch protection settings?
* Pinned Dependencies: Has the project declared and pinned its dependencies?
* Dangerous Workflow: Does the project's GitHub Action workflows avoid dangerous patterns?
* Static Application Security Testing (SAST): Does the project use static code analysis?
* Dependency Update Tool: Does the project use a dependency update tool?
* Security Policy: Has the project published a security policy?
* Fuzzing: Does the project use fuzzing in OSS-Fuzz?
* Token Permissions: Is the project following the principle of least privilege?
* Packaging: Has the project been published as a package that others can easily download, install, update, and uninstall?
* Webhooks: Are the webhooks defined in the repository token configured?

### Understanding Security Posture

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2F7TKGrBE4lJqsswcsvYQs%2Fimage.png?alt=media&amp;token=6b308193-7208-499e-81ec-929e4dd2563d" alt=""><figcaption></figcaption></figure>

* Count of components that have security posture issues is displayed towards left, along with the category of the components (open-source, private, third-party, unknown).
* The security posture issue count is displayed towards the right, grouped by severity (critical, high, medium, low).
* Each tile is clickable which will list down the components applicable to that filter in a table view. The details will list the component name, version and a capsule for security posture checks.
* By clicking the security posture checks capsule, next level details will be shown as below.
* By clicking on any row, the sidesheet shows up as shown below.

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FXgxxgLg8uZKkzWU7oha8%2Fimage.png?alt=media&amp;token=45bcfb52-337b-4797-ad6b-18b286454c2a" alt=""><figcaption></figcaption></figure>

<br>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/projects/security-posture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
