-
- - In the `Security` section of the sidebar, select `Secrets and variables`, then click `Actions`.
-
- - At the top of the page, click `New repository secret`.
-
- - Type 'SCRIBE_TOKEN' as name for your secret in the `Name` input box.
-
- - Enter the value for your token.
-
- - Click `Add secret`.
-
-5. You can now run a workflow to create an attestation of the last version committed and pushed to Git. This attestation represents the 'source of truth' regarding the project's source code. Once you have created and stored this attestation it is quite difficult for a potential adversary to tamper with the code anywhere down the pipeline. In the demo project page, go to Actions.
-Click ‘I understand my workflows, go ahead and enable them’.
-
- 
-
-You will be redirected to the 'Actions' tab:
-
- 
-
- From the actions available on the left panel select *`Create signed git commit sbom`* and click `Run workflow`. Once the workflow finished executing, a signed attestation (an SBOM) has been generated and automatically uploaded to your Scribe Hub account.
-
-6. At this point you can run the build pipeline - build the project and containerize it. You can do this by running the *`Create signed git clone and signed image SBOMs`* workflow. As the name suggests, this workflow will generate a signed SBOM of the git repo cloned into the pipeline and another signed SBOM of the final built docker image.
-
- Both attestations will be uploaded to your Scribe Hub account. Now you can view the project details on the **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** **products** page of your Scribe Hub account.
-
-### Quick tour of the Scribe Hub
-
-The first page you see when you log into your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** is your **Products** page.
-
-
-
-You will see a demo project. Since you have just run the sample project's workflows, running a pipeline, generating evidence, and uploading it to Scribe Hub, you'll see your new project under the default demo project.
-
-The **Products** page shows you your products along with some basic information: How many subscribers have you added to this product, when the latest version of it was created (the last pipeline run), how many components were identified in the project, if the source code integrity was verified or not, how many high (or higher) vulnerabilities were identified, and how the project stands in terms of compliance to the SSDF and SLSA frameworks.
-
-Clicking on a product will show you all the product's builds and their information:
-
-
-
-For each build you can see its version ID, the build date, if the source code integrity was verified or not, the number and severity of vulnerabilities, how that build stands in terms of compliance, whether the build was published and if its signature was verified.
-
-for more information click on any of the builds and you'll get to the build dashboard:
-
-
-
-The dashboard is your main access to see this build's reports. You can see a summary of the build's compliance information to each of the frameworks, you can see a summary of the vulnerability information, and you can see the integrity validation information.
-
-### Where to go next
-* To learn more about what you can see, learn, and access about your build and your product look at the **[reports guide](../scribe-hub-reports/)** section.
-* To learn how to create and manage SBOMs and vulnerabilities go to this **[guide](../guides/manag-sbom-and-vul)**.
-* To learn about Scribe's use of the SLSA framework go to this **[guide](../guides/secure-sfw-slsa)**.
-* To learn about enforcing SDLC policies go to this **[guide](../guides/enforcing-sdlc-policy)**.
-* To learn how to achieve SSDF compliance go to this **[guide](../guides/ssdf-compliance)**.
-* To learn how to secure your builds go to this **[guide](../guides/securing-builds)**.
diff --git a/docs/quick-start/set-up-integration/_category_.json b/docs/quick-start/set-up-integration/_category_.json
deleted file mode 100644
index 9b4abfe84..000000000
--- a/docs/quick-start/set-up-integration/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Setting up an integration",
- "position": 2
-}
\ No newline at end of file
diff --git a/docs/quick-start/set-up-integration/set-up-azure.md b/docs/quick-start/set-up-integration/set-up-azure.md
deleted file mode 100644
index a62c3777b..000000000
--- a/docs/quick-start/set-up-integration/set-up-azure.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-sidebar_label: "Azure"
-sidebar_position: 3
-title: Setting up an integration in Azure Pipelines
-toc_min_heading_level: 2
-toc_max_heading_level: 5
----
-
-### The steps to take to integrate Azure Pipelines with Scribe Hub
-
-1. If you haven't yet done so, open a free Scribe Hub account **[here](https://scribesecurity.com/scribe-platform-lp/ "Start Using Scribe For Free")**.
-
-
-2. Get your **Client Secret** credentials from your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** **Integrations** page.
-
-
-
-3. Login to your **[Azure](https://portal.azure.com/#home)** account.
-
-4. Follow the **[install-an-extension](https://learn.microsoft.com/en-us/azure/devops/marketplace/install-extension?view=azure-devops&tabs=browser#install-an-extension)** instructions to install our **[Valint-task](https://marketplace.visualstudio.com/items?itemName=ScribeSecurity.valint-cli)** from the Azure marketplace.
-
-
- -
- -
- -
- -
- -
- -
-
-4. Create a new project or go to an existing project
-
-
-
-5. Inside the project create a new repository (repo) if you don't already have one you want to use Valint with an Azure pipeline on
-
-
-
-
-
-6. Open your Azure DevOps project repository and make sure you have a YAML file named `azure-pipelines.yml` Or just click on `Create a new pipeline`.
-
-
-
-
-
-7. Add the Scribe code example shown below to your `azure-pipelines.yml` file.
-
-:::note
-***[Refer to this Azure document to configure runners.](https://learn.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops#:~:text=Manage%20agents%20%26%20self%2Dhosted%20agents)***
-:::
-
-```yaml
-trigger:
- branches:
- include:
- - main
-
-jobs:
-- job: scribe_azure_job
- displayName: 'Scribe Azure Job'
- pool:
- name: {Update pool name here} # Example: Mikey
- agent: {Update agent name here} # Example: azure-runner-ubuntu
-
- variables:
- imageName: 'pipelines-javascript-docker'
-
- steps:
- - task: scribeInstall@0
-
- - task: ValintCli@0
- inputs:
- command: bom
- target: nginx
- format: statement
- outputDirectory: $(Build.ArtifactStagingDirectory)/scribe/valint
- scribeEnable: true
- scribeClientId: $(CLIENTID)
- scribeClientSecret: $(CLIENTSECRET)
-
- - task: ValintCli@0
- inputs:
- command: verify
- target: nginx
- inputFormat: statement
- outputDirectory: $(Build.ArtifactStagingDirectory)/scribe/valint
- scribeEnable: true
- scribeClientId: $(CLIENTID)
- scribeClientSecret: $(CLIENTSECRET)
-```
-
-
-8. Add the credentials to your Azure environment according to the **[Azure DevOps - Set secret variables](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/set-secret-variables?view=azure-devops&tabs=yaml%2Cbash "Azure DevOps - Set secret variables")**:
- * Go to the **Pipelines** page, select the appropriate pipeline, and then select **Edit**.
- * Locate the **Variables** for this pipeline.
-
- 
-
- * Add or update the variable.
-
- 
-
- 
-
- * Select the **Secret** lock icon to store the variable in an encrypted manner.
-
- 
-
- * **Save** the pipeline.
-
- 
-
-9. You can now run the pipeline you created for your repository.
-
-
-
-
-
-10. To add your own policies to the pipeline check out **[this guide](../../guides/enforcing-sdlc-policy#policies-and-policy-modules)**.
-
-11. To capture 3rd party tool results in the pipeline and turn it into evidence, check out **[this guide](../../guides/manag-sbom-and-vul#ingesting-reports-from-application-security-scanners)**.
-
-### Where to go on Scribe Hub
-
-Now that you've created your first set of evidence you can log into your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** to view the results.
-
-The first place you can look into to make sure your evidence has been uploaded properly is the **[Evidence report](../../scribe-hub-reports/evidence)**. The evidence report shows all the evidence you have collected and uploaded to Scribe Hub from all your pipelines and projects.
-
-To see more details on your pipeline you can check out the **[Product page](../../scribe-hub-reports/product)**
-
-
-
-The **products** page shows you your products along with some basic information: How many subscribers have you added to this product, when the latest version of it was created (the last pipeline run), how many components were identified in the project, if the source code integrity was verified or not, how many high (or higher) vulnerabilities were identified, and how the project stands in terms of compliance to the SSDF and SLSA frameworks.
-
-Clicking on a product will show you all the product's builds and their information:
-
-
-
-For each build you can see its version ID, the build date, if the source code integrity was verified or not, the number and severity of vulnerabilities, how that build stands in terms of compliance, whether the build was published and if its signature was verified.
-
-for more information on the pipeline you just completed, click on the last build uploaded (the top of the list) and you'll get to the build dashboard:
-
-
-
-The dashboard is your main access to see this build's **[reports](../../scribe-hub-reports/)**. You can see a summary of the build's compliance information to each of the frameworks, you can see a summary of the vulnerability information, and you can see the integrity validation information.
-
-### Where to go next
-* To learn more about what you can see, learn, and access about your build and your product look at the **[reports guide](../../scribe-hub-reports/)** section.
-* To learn how to create and manage SBOMs and vulnerabilities go to this **[guide](../../guides/manag-sbom-and-vul)**.
-* To learn about Scribe's use of the SLSA framework go to this **[guide](../../guides/secure-sfw-slsa)**.
-* To learn about enforcing SDLC policies go to this **[guide](../../guides/enforcing-sdlc-policy)**.
-* To learn how to achieve SSDF compliance go to this **[guide](../../guides/ssdf-compliance)**.
-* To learn how to secure your builds go to this **[guide](../../guides/securing-builds)**.
diff --git a/docs/quick-start/set-up-integration/set-up-github.md b/docs/quick-start/set-up-integration/set-up-github.md
deleted file mode 100644
index 79eada73b..000000000
--- a/docs/quick-start/set-up-integration/set-up-github.md
+++ /dev/null
@@ -1,335 +0,0 @@
----
-sidebar_label: "GitHub"
-title: Setting up an integration in GitHub
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 5
----
-
-### The steps to take to integrate a GitHub repository with Scribe Hub
-
-1. If you haven't yet done so, open a free Scribe Hub account **[here](https://scribesecurity.com/scribe-platform-lp/ "Start Using Scribe For Free")**.
-
-
-2. Get your **Client Secret** credentials from your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** **Integrations** page.
-
-
-
-3. Login to your **[GitHub](https://github.com)** account.
-
-4. Go to the repository you wish to integrate with Scribe.
-
-5. Define two new `Secret` variables for your repository.
-To do that, go to settings → Secrets and variables → Actions → New repository secret.
-
- - Under your repository name, click `Settings`. If you cannot see the `Settings` tab, select the dropdown menu, then click `Settings`.
-
- 
-
- - In the `Security` section of the sidebar, select `Secrets and variables`, then click `Codespaces`.
-
- 
-
-
- - At the top of the new page, click the green `New repository secret` button.
-
- 
-
- - Type a name for your secret in the `Name` input box. you need to add each secret in turn, first `CLIENT_ID` and then `CLIENT_SECRET`. Enter the value for your secret. In both cases the secret value is the one you get from your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** **Integrations** page.
-
- 
-
- - Click `Add secret`.
-
- 
-
-6. Now that you have added the `CLIENT_ID` and `CLIENT_SECRET` variables to your repository you can add the Scribe code snippets into your YAML workflows. This guide assumes you're adding all possible evidence collection points.
-
- -
- 
-
- If the folder dosn't exist, create it.
-
- In the folder create a new file called `create-signed-git-commit-sbom.yml`. Here's the file's code:
-
- ```yaml
- name: Create signed git commit sbom
-
- on: push
-
- build:
- runs-on: ubuntu-latest
-
- permissions:
- id-token: write # workload identity access needed for signing using sigstore-github
-
- steps:
- - uses: actions/checkout@v3
-
- - name: Generate signed git SBOM
- uses: scribe-security/action-bom@master
- with:
- target: 'git:.'
- product-key: ${{ github.repository }}
- scribe-client-secret: ${{ secrets.CLIENT_SECRET }}
- label: is_git_commit
- format: attest
-
- ```
-
- The `on: push` segment of this workflow means that whenever there is a `push` into this repository, a new signed SBOM of the repository will be sent to the evidence store of your Scribe hub.
-
- Once this evidence is uploaded to your Scribe Hub you'd be able to see it on your **[evidence report](../../scribe-hub-reports/evidence)**.
-
-
-
- - To add automatic evidence collection (a signed SBOM) after each commit
- - Assuming that you do not yet have an existing pipeline workflow, you need to create a new YAML file under the `.github/workflows/` folder in the root folder of your repository. - -
-
- If the folder dosn't exist, create it.
-
- In the folder create a new file called `create-signed-git-commit-sbom.yml`. Here's the file's code:
-
- ```yaml
- name: Create signed git commit sbom
-
- on: push
-
- build:
- runs-on: ubuntu-latest
-
- permissions:
- id-token: write # workload identity access needed for signing using sigstore-github
-
- steps:
- - uses: actions/checkout@v3
-
- - name: Generate signed git SBOM
- uses: scribe-security/action-bom@master
- with:
- target: 'git:.'
- product-key: ${{ github.repository }}
- scribe-client-secret: ${{ secrets.CLIENT_SECRET }}
- label: is_git_commit
- format: attest
-
- ```
-
- The `on: push` segment of this workflow means that whenever there is a `push` into this repository, a new signed SBOM of the repository will be sent to the evidence store of your Scribe hub.
-
- Once this evidence is uploaded to your Scribe Hub you'd be able to see it on your **[evidence report](../../scribe-hub-reports/evidence)**.
-
-
-
-
- This new file is going to be your GitHub pipeline to create the final image from your repository.
-
- If you already have an existing pipeline workflow open the YAML file.
-
- You need to add Scribe code snippets in 2 main locations:
-
-
- - If you are building multiple images, make sure you add the second Scribe code snippet (`Generate signed SBOM for docker image`) after each one. - - Since each pipeline is different this example will only contain just the Scribe code as an example. - - ```yaml - name: Create signed git clone and image SBOMs - - on: workflow_dispatch - - jobs: - - build: - runs-on: ubuntu-latest - - permissions: - contents: read - packages: write - id-token: write - - steps: - - uses: actions/checkout@v3 - - - name: Generate signed SBOM for repo content - # Used after git clone at the begining of the pipeline - uses: scribe-security/action-bom@master - with: - target: 'git:.' - components: packages,files,dep - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Build the Docker image - # This is a stand in step for whatever needs to happen in your pipeline culminating with building a docker image from the repository - run: docker build . -t ${{ github.repository }}:${{ github.sha }} - - - name: Generate signed SBOM for docker image - # Used after a docker image is built - uses: scribe-security/action-bom@master - with: - target: 'docker:scribe-demo-product:${{ github.sha }}' - - product-key: ${{ github.repository }}:${{ github.sha }} - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - ``` - - Every time you run the workflow the evidence will be generated and uploaded to your Scribe Hub automatically. You'd be able to see the evidence on your **[evidence report](../../scribe-hub-reports/evidence)**. - - You'll also see a new build version added to the appropriate project: - -
-
- Clicking on the latest added build will allow you to explore all it's relevent information, **[reports](../../scribe-hub-reports)**, and insights through the build dashboard:
-
-
-
-
-
- - To add automatic evidence collection (a signed SBOM) to your GitHub pipeline workflow
- - Assuming that you do not yet have an existing pipeline workflow, you need to create a new YAML file under the `.github/workflows/` folder in the root folder of your repository. - -
-
- This new file is going to be your GitHub pipeline to create the final image from your repository.
-
- If you already have an existing pipeline workflow open the YAML file.
-
- You need to add Scribe code snippets in 2 main locations:
-
- -
-
- Right after the code pull at the start of the pipeline. -
- Right after the image is built at the end of the pipeline. -
- - If you are building multiple images, make sure you add the second Scribe code snippet (`Generate signed SBOM for docker image`) after each one. - - Since each pipeline is different this example will only contain just the Scribe code as an example. - - ```yaml - name: Create signed git clone and image SBOMs - - on: workflow_dispatch - - jobs: - - build: - runs-on: ubuntu-latest - - permissions: - contents: read - packages: write - id-token: write - - steps: - - uses: actions/checkout@v3 - - - name: Generate signed SBOM for repo content - # Used after git clone at the begining of the pipeline - uses: scribe-security/action-bom@master - with: - target: 'git:.' - components: packages,files,dep - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Build the Docker image - # This is a stand in step for whatever needs to happen in your pipeline culminating with building a docker image from the repository - run: docker build . -t ${{ github.repository }}:${{ github.sha }} - - - name: Generate signed SBOM for docker image - # Used after a docker image is built - uses: scribe-security/action-bom@master - with: - target: 'docker:scribe-demo-product:${{ github.sha }}' - - product-key: ${{ github.repository }}:${{ github.sha }} - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - ``` - - Every time you run the workflow the evidence will be generated and uploaded to your Scribe Hub automatically. You'd be able to see the evidence on your **[evidence report](../../scribe-hub-reports/evidence)**. - - You'll also see a new build version added to the appropriate project: - -
-
- Clicking on the latest added build will allow you to explore all it's relevent information, **[reports](../../scribe-hub-reports)**, and insights through the build dashboard:
-
-
-
-
-
- - Now that you have connected the Scribe GitHub app to your organizational GitHub account you can add the SLSA provenance generation code snipet to the end of your build pipeline. - - Here's the code you should add to your pipeline workflow YAML file after the final docker image is created: - - ```yaml - - name: Generate SLSA provenance statement - id: valint_slsa_statement - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - format: statement-slsa - - -uses: actions/upload-artifact@v4 - with: - name: provenance - path: ${{ steps.valint_slsa_statement.outputs.OUTPUT_PATH }} - - ``` - - And here's a full example pipeline: - - ```yaml - name: Create signed git clone and image SBOMs - - on: workflow_dispatch - - jobs: - - build: - runs-on: ubuntu-latest - - permissions: - contents: read - packages: write - id-token: write - - steps: - - uses: actions/checkout@v3 - - - name: Generate signed SBOM for repo content - # Used after git clone at the begining of the pipeline - uses: scribe-security/action-bom@master - with: - target: 'git:.' - components: packages,files,dep - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Build the Docker image - # This is a stand in step for whatever needs to happen in your pipeline culminating with building a docker image from the repository - run: docker build . -t ${{ github.repository }}:${{ github.sha }} - - - name: Generate signed SBOM for docker image - # Used after a docker image is built - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - product-key: ${{ github.repository }}:${{ github.sha }} - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Generate SLSA provenance statement - id: valint_slsa_statement - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - format: statement-slsa - - -uses: actions/upload-artifact@v4 - with: - name: provenance - path: ${{ steps.valint_slsa_statement.outputs.OUTPUT_PATH }} - ``` - - To see that provenance information you need to go to the **Actions** tab in your GitHub repository. - -
-
- There you can examine the workflows and actions you have run on this GitHub repository. Once you have run a workflow that includes the SLSA provenance generation you'll be able to find the resulting file at the bottom of the page:
-
- 
-
- The provenance information is in in-toto format and looks like this:
-
- 
-
- In your Scribe hub, having a SLSA provenance added can be seen in your **[compliance report](../../scribe-hub-reports/compliance)**:
-
- 
-
-
-
-7. To add your own policies to the pipeline check out **[this guide](../../guides/enforcing-sdlc-policy#policies-and-policy-modules)**.
-
-8. To capture 3rd party tool results in the pipeline and turn it into evidence, check out **[this guide](../../guides/manag-sbom-and-vul#ingesting-reports-from-application-security-scanners)**.
-
-### Where to go on Scribe Hub
-
-Now that you've created your first set of evidence you can log into your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** to view the results.
-
-The first place you can look into to make sure your evidence has been uploaded properly is the **[Evidence report](../../scribe-hub-reports/evidence)**. The evidence report shows all the evidence you have collected and uploaded to Scribe Hub from all your pipelines and projects.
-
-To see more details on your pipeline you can check out the **Product page**
-
-To add SLSA provenance statement collection to your GitHub pipeline workflow
- - In order to add SLSA provenance generation to your GitHub pipeline workflow you must first connect the Scribe GitHub app to your organizational GitHub account. - - To do that: - --
-
-
- To start the integration go to your [Scribe Hub account](https://scribehub.scribesecurity.com/ "Scribe Hub Link"). On the left options column go to the integrations option.
-
-
- -
- On the integrations page scroll down to the Source Control section:
-
-
- -
- Press the connect button. That will lead you to a page like this:
-
-
- -
- Choose the GitHub account you want to integrate the ScribeApp with. Make sure you have owner access to the account to allow the app integration. Make sure the account is organizational - the integration won't work with a private account.
- Once you have chosen the account you wish to integrate with ScribeApp GitHub you will get the following window:
-
-
- -
- Choose the access level you wish to grant ScribeApp. You can choose to allow it access to all repositories or just select repositories. Note that repositories that are not covered by the ScribeApp will not be able to produce the SLSA provenance.
- After reviewing the access granted to ScribeApp go ahead and approve it by pressing the big green button.
-
-
- -
- Next, you'll be directed to GitHub to approve your access by inputting your password.
-
-
- -
- You get redirected to the integrations page. There is now a green checkmark next to the GitHub icon in the Source Control section:
-
-
-
- - Now that you have connected the Scribe GitHub app to your organizational GitHub account you can add the SLSA provenance generation code snipet to the end of your build pipeline. - - Here's the code you should add to your pipeline workflow YAML file after the final docker image is created: - - ```yaml - - name: Generate SLSA provenance statement - id: valint_slsa_statement - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - format: statement-slsa - - -uses: actions/upload-artifact@v4 - with: - name: provenance - path: ${{ steps.valint_slsa_statement.outputs.OUTPUT_PATH }} - - ``` - - And here's a full example pipeline: - - ```yaml - name: Create signed git clone and image SBOMs - - on: workflow_dispatch - - jobs: - - build: - runs-on: ubuntu-latest - - permissions: - contents: read - packages: write - id-token: write - - steps: - - uses: actions/checkout@v3 - - - name: Generate signed SBOM for repo content - # Used after git clone at the begining of the pipeline - uses: scribe-security/action-bom@master - with: - target: 'git:.' - components: packages,files,dep - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Build the Docker image - # This is a stand in step for whatever needs to happen in your pipeline culminating with building a docker image from the repository - run: docker build . -t ${{ github.repository }}:${{ github.sha }} - - - name: Generate signed SBOM for docker image - # Used after a docker image is built - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - product-key: ${{ github.repository }}:${{ github.sha }} - scribe-client-secret: ${{ secrets.CLIENT_SECRET }} - format: attest - - - name: Generate SLSA provenance statement - id: valint_slsa_statement - uses: scribe-security/action-bom@master - with: - target: 'docker:${{ github.repository }}:${{ github.sha }}' - format: statement-slsa - - -uses: actions/upload-artifact@v4 - with: - name: provenance - path: ${{ steps.valint_slsa_statement.outputs.OUTPUT_PATH }} - ``` - - To see that provenance information you need to go to the **Actions** tab in your GitHub repository. - -
-
- There you can examine the workflows and actions you have run on this GitHub repository. Once you have run a workflow that includes the SLSA provenance generation you'll be able to find the resulting file at the bottom of the page:
-
-
-
- The provenance information is in in-toto format and looks like this:
-
-
-
- In your Scribe hub, having a SLSA provenance added can be seen in your **[compliance report](../../scribe-hub-reports/compliance)**:
-
-
-
-
-
-The **products** page shows you your products along with some basic information: How many subscribers have you added to this product, when the latest version of it was created (the last pipeline run), how many components were identified in the project, if the source code integrity was verified or not, how many high (or higher) vulnerabilities were identified, and how the project stands in terms of compliance to the SSDF and SLSA frameworks.
-
-Clicking on a product will show you all the product's builds and their information:
-
-
-
-For each build you can see its version ID, the build date, if the source code integrity was verified or not, the number and severity of vulnerabilities, how that build stands in terms of compliance, whether the build was published and if its signature was verified.
-
-for more information on the pipeline you just completed, click on the last build uploaded (the top of the list) and you'll get to the build dashboard:
-
-
-
-The dashboard is your main access to see this build's **[reports](../../scribe-hub-reports/)**. You can see a summary of the build's compliance information to each of the frameworks, you can see a summary of the vulnerability information, and you can see the integrity validation information.
-
-### Where to go next
-* To learn more about what you can see, learn, and access about your build and your product look at the **[reports guide](../../scribe-hub-reports/)** section.
-* To learn how to create and manage SBOMs and vulnerabilities go to this **[guide](../../guides/manag-sbom-and-vul)**.
-* To learn about Scribe's use of the SLSA framework go to this **[guide](../../guides/secure-sfw-slsa)**.
-* To learn about enforcing SDLC policies go to this **[guide](../../guides/enforcing-sdlc-policy)**.
-* To learn how to achieve SSDF compliance go to this **[guide](../../guides/ssdf-compliance)**.
-* To learn how to secure your builds go to this **[guide](../../guides/securing-builds)**.
-
-
-
diff --git a/docs/quick-start/set-up-integration/set-up-jenkins.md b/docs/quick-start/set-up-integration/set-up-jenkins.md
deleted file mode 100644
index 31bd4fc5b..000000000
--- a/docs/quick-start/set-up-integration/set-up-jenkins.md
+++ /dev/null
@@ -1,180 +0,0 @@
----
-sidebar_position: 2
-sidebar_label: "Jenkins"
-title: Setting up an integration in Jenkins
-toc_min_heading_level: 2
-toc_max_heading_level: 5
----
-
-### The steps to take to integrate Jenkins with Scribe Hub
-
-1. If you haven't yet done so, open a free Scribe Hub account **[here](https://scribesecurity.com/scribe-platform-lp/ "Start Using Scribe For Free")**.
-
-
-2. Get your **Client Secret** credentials from your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** **Integrations** page.
-
-
-
-3. Login to your Jenkins Web Console.
- 
-
-4. Select **Dashboard> Manage Jenkins> Manage credentials (under Security options)**.
- 
-
-5. Select 'Global' in the list of domains:
- 
-
-6. To add Client Secret, in the **Global credentials** area, click **+ Add Credentials**. A new **Credentials** form will open.
- 
-
-7. Apply the **Client Secret** provided by Scribe to the **Password**, Username can be filled in with anything.
- 
-
-8. Set **ID** to **`scribe-auth-id`** (lowercase).
- 
-
-9. Click **Create**.
- 
-
-10. Click on 'Dashboard' to go to the main dashboard
- 
-
-11. Click on 'New Item'
- 
-
-12. Create a new folder such as 'integration-scribe-in-jenkins'. Click on 'New Folder' to create it once you enter the name and then click 'ok'.
- 
-
-13. Click 'Apply' and then 'Save'.
- 
-
-14. Now to create the pipeline, click on 'New Item'
- 
-
-15. Name it 'install-valint-pipeline'. Click on 'New Pipeline' to create it once you enter the name and then click 'ok'.
- 
-
-16. Once you created a pipeline a new job is created. Click on the job:
- 
-
-17. Scroll down till you reach a 'pipeline' section and add the following script:
- 
-
-### Jenkins pipeline JavaScript code example
-
-```javascript
-pipeline {
- agent any
- stages {
- stage('checkout') {
- steps {
- cleanWs()
- sh 'git clone -b v1.0.0-alpha.4 --single-branch https://github.com/mongo-express/mongo-express.git mongo-express-scm'
- }
- }
-
- stage('sbom') {
- agent {
- docker {
- image 'scribesecurity/valint:latest'
- reuseNode true
- args "--entrypoint="
- }
- }
- steps {
- withCredentials([token(credentialsId: 'scribe-auth-id', variable: 'SCRIBE_TOKEN')]) {
- sh '''
- valint bom dir:mongo-express-scm \
- --context-type jenkins \
- --output-directory ./scribe/valint \
- -P $SCRIBE_TOKEN '''
- }
- }
- }
-
- stage('image-bom') {
- agent {
- docker {
- image 'scribesecurity/valint:latest'
- reuseNode true
- args "--entrypoint="
- }
- }
- steps {
- withCredentials([token(credentialsId: 'scribe-auth-id', variable: 'SCRIBE_TOKEN')]) {
- sh '''
- valint bom mongo-express:1.0.0-alpha.4 \
- --context-type jenkins \
- --output-directory ./scribe/valint \
- -P $SCRIBE_TOKEN '''
- }
- }
- }
- }
-}
-```
-:::note
-The above pipeline script is an example. It connects to the GitHub repository [https://github.com/mongo-express/mongo-express.git](https://github.com/mongo-express/mongo-express.git), clones it and creates an image for it.
-
-An SBOM is created after the clone is done and after the image has been created.
-
-The above example was created under the assumption that you're using **Jenkins over Docker**. If you have a different version of Jenkins like **Jenkins over Kubernetes (K8s)** or **Jenkins Vanilla (No Agent)** you can find the needed JavaScript needed to create your pipeline in our full **[Jenkins Documentation](../../integrating-scribe/ci-integrations/jenkins#procedure)**.
-:::
-
-18. Click 'Apply' and then 'Save'.-
-
-19. Click on 'Build now' to run the pipeline:
- 
-
-20. Click on the '#' to see the pipeline log output
- 
- 
-
-21. To add your own policies to the pipeline check out **[this guide](../../guides/enforcing-sdlc-policy#policies-and-policy-modules)**.
-
-22. To capture 3rd party tool results in the pipeline and turn it into evidence, check out **[this guide](../../guides/manag-sbom-and-vul#ingesting-reports-from-application-security-scanners)**.
-
-
-
-### Where to go on Scribe Hub
-
-Now that you've created your first set of evidence you can log into your **[Scribe Hub](https://scribehub.scribesecurity.com/ "Scribe Hub Link")** to view the results.
-
-The first place you can look into to make sure your evidence has been uploaded properly is the **[Evidence report](../../scribe-hub-reports/evidence)**. The evidence report shows all the evidence you have collected and uploaded to Scribe Hub from all your pipelines and projects.
-
-To see more details on your pipeline you can check out the **Product page**
-
-
-
-The **products** page shows you your products along with some basic information: How many subscribers have you added to this product, when the latest version of it was created (the last pipeline run), how many components were identified in the project, if the source code integrity was verified or not, how many high (or higher) vulnerabilities were identified, and how the project stands in terms of compliance to the SSDF and SLSA frameworks.
-
-Clicking on a product will show you all the product's builds and their information:
-
-
-
-For each build you can see its version ID, the build date, if the source code integrity was verified or not, the number and severity of vulnerabilities, how that build stands in terms of compliance, whether the build was published and if its signature was verified.
-
-for more information on the pipeline you just completed, click on the last build uploaded (the top of the list) and you'll get to the build dashboard:
-
-
-
-The dashboard is your main access to see this build's **[reports](../../scribe-hub-reports/)**. You can see a summary of the build's compliance information to each of the frameworks, you can see a summary of the vulnerability information, and you can see the integrity validation information.
-
-### Where to go next
-* To learn more about what you can see, learn, and access about your build and your product look at the **[reports guide](../../scribe-hub-reports/)** section.
-* To learn how to create and manage SBOMs and vulnerabilities go to this **[guide](../../guides/manag-sbom-and-vul)**.
-* To learn about Scribe's use of the SLSA framework go to this **[guide](../../guides/secure-sfw-slsa)**.
-* To learn about enforcing SDLC policies go to this **[guide](../../guides/enforcing-sdlc-policy)**.
-* To learn how to achieve SSDF compliance go to this **[guide](../../guides/ssdf-compliance)**.
-* To learn how to secure your builds go to this **[guide](../../guides/securing-builds)**.
diff --git a/docs/release-notes/rns.md b/docs/release-notes/rns.md
index 3a12a7a5b..d74bcb370 100644
--- a/docs/release-notes/rns.md
+++ b/docs/release-notes/rns.md
@@ -1,21 +1,67 @@
-# Scribe Hub
-*Last modified November 3, 2024*
-## Scribe Hub Version 1.23.0
-*Novemeber 4, 2024*
+# Scribe Hub
+*Last modified: May 29, 2025*
+---
+
+## Version 1.43.2 (May 29, 2025)
+
+### Improvements
+- Under **Products ▸ `
+For working usage examples, visit our **[GitHub repository](https://github.com/scribe-security/api-examples)**.
-The response to the token request looks like this:
-```
-{
- "access_token":"eyJz93a...k4laUWw",
- "token_type":"Bearer",
- "expires_in":86400
-}
-```
-The `access_token` in the response is your API key.
+## Steps to Access the API
-Scribe uses **[swagger-client](https://www.npmjs.com/package/swagger-client)** to enable access to our API. Swagger-client is a JavaScript module that allows you to fetch, resolve, and interact with OpenAPI documents to resolve API calls.
+Follow these steps to authenticate and start using the Scribe API:
-To use it you should first download and install swagger-client. If the Python package is hosted on GitHub, you can install it directly from GitHub
+1. **Generate an API Token**
+ - Navigate to **[Scribe Hub > Account > Tokens](https://app.scribesecurity.com/account/tokens)**.
+ - Create a new API token.
-```sh
-pip install git+https://github.com//.git
-```
-(you may need to run `pip` with root permission: `sudo pip install git+https://github.com//.git`)
+2. **Obtain a JWT Token**
+ - Call the `/v1/login` API endpoint.
+ - Refer to the **[Swagger documentation](https://api.scribesecurity.com/v1/swaggerui#/login)** for request details.
+ - The `access_token` in the response is your API key.
-Then import the package:
-```python
-import swagger_client
-```
-
-### Setuptools
-
-Install via [Setuptools](http://pypi.python.org/pypi/setuptools).
-
-```sh
-python setup.py install --user
-```
-(or `sudo python setup.py install` to install the package for all users)
-
-Then import the package:
-```python
-import swagger_client
-```
-
-## Getting Started
-
-Please follow the installation procedure and then run the following:
-
-```python
-from __future__ import print_function
-import time
-import swagger_client
-from swagger_client.rest import ApiException
-from pprint import pprint
-
-# Configure API key authorization: JWT
-configuration = swagger_client.Configuration()
-configuration.api_key['Authorization'] = 'YOUR_API_KEY'
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['Authorization'] = 'Bearer'
-
-# create an instance of the API class
-api_instance = swagger_client.DatasetApi(swagger_client.ApiClient(configuration))
-body = swagger_client.LoginRequest() # LoginRequest | (optional)
-
-try:
- # This endpoint is used to get an admin token, either use client-id and secret OR the refresh token.
- api_response = api_instance.get_admin_token_action(body=body)
- pprint(api_response)
-except ApiException as e:
- print("Exception when calling DatasetApi->get_admin_token_action: %s\n" % e)
-
-```
-
-## Documentation for API Endpoints
-
-All URIs are relative to *http://localhost:4000*
-
-Class | Method | HTTP request | Description
------------- | ------------- | ------------- | -------------
-*DatasetApi* | get_admin_token_action | **GET** /dataset/token | This endpoint is used to get an admin token, either use client-id and secret OR the refresh token.
-*DatasetApi* | get_datasets_action | **POST** /dataset/data | This endpoint is used to retrieve data from a dataset with a filter.
-*DatasetApi* | list_datasets_input_action | **GET** /dataset | This endpoint is used to list the available datasets with their schema.
-*DefaultApi* | dataset | **POST** /dataset/token | This endpoint is used to exchange a team product key with a superset data-access token.
-*EvidenceApi* | delete_evidence_action | **DELETE** /evidence/\{file_id\} | Delete evidence object.
-*EvidenceApi* | download_evidence_action | **GET** /evidence/\{file_id\} | Create pre-signed URL to POST file content.
-*EvidenceApi* | finish_upload_evidence_action | **POST** /evidence/finish | Mark file transfer as finished.
-*EvidenceApi* | list_evidence_action | **POST** /evidence/list | Get a list of processes for specific queries.
-*EvidenceApi* | upload_evidence_action | **POST** /evidence | Create pre-signed URL to POST file content.
-
-
-
-### API Usage Examples
-
-You can find working usage examples **[here](https://github.com/scribe-security/api-examples)**.
\ No newline at end of file
+Once authenticated, you can use this token to access other API endpoints securely.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 09bc040e5..2e9fcbf6b 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -85,10 +85,7 @@ const config = {
"introducing-scribe/what-is-scribe.md",
"introducing-scribe/scribe-hub.md",
"introducing-scribe/stand-alone.md",
- "quick-start/demo.md",
- "quick-start/set-up-integration/set-up-github.md",
- "quick-start/set-up-integration/set-up-jenkins.md",
- "quick-start/set-up-integration/set-up-azure.md",
+ "quick-start/README.md",
"guides/manag-sbom-and-vul.md",
"guides/secure-sfw-slsa/README.md",
"guides/secure-sfw-slsa/slsa-lvl-1.md",