Skip to content

Commit fd69e5c

Browse files
authored
Linked SBOM page, added scheduled run to update SBOM reports after new SBOMs are generated (#103)
* Added scheduled run * Linked sbom page
1 parent f7b9d05 commit fd69e5c

File tree

3 files changed

+15
-5
lines changed

3 files changed

+15
-5
lines changed

.github/workflows/deploy.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ on:
44
push:
55
branches:
66
- main
7+
schedule:
8+
- cron: '30 3 * * *' # 3:30 AM UTC (SBOMs regenerate at 2:30 AM UTC)
79

810
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
911
permissions:

src/pages/sbom.astro

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ const tags = [
128128
<Navigation activeSlug="/security/" />
129129

130130
<main id="home-page">
131-
<FlexibleSection leftRatio={1} title="What is SBOM?" theme="light">
131+
<FlexibleSection leftRatio={1} title="What is SBOM?" theme="light" id="what-is-sbom">
132132
<div slot="left" class="sbom-intro">
133133
<p>
134134
A <strong>Software Bill of Materials (SBOM)</strong> is a structured inventory of all components that make up
@@ -151,7 +151,7 @@ const tags = [
151151
</FlexibleSection>
152152

153153

154-
<FlexibleSection leftRatio={1} title="SBOM file list with vulnerability status" theme="light">
154+
<FlexibleSection leftRatio={1} title="SBOM file list with vulnerability status" theme="light" id="sbom-list">
155155
<div slot="left" class="sbom-filelist">
156156
<p>
157157
Separate SBOMs are available for <strong>mobile apps</strong> (Android, iOS), the <strong>desktop app</strong>

src/pages/security.astro

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,9 @@ const tags = [
4545
title="Our Security Approach"
4646
description="Building a secure software is a mindset. Features, great UI, and easy deployment are often things that draw users to the software, but when building software in the cybersecurity space, the approach to security should be what tips the scales of choice. Here is ours."
4747
buttons={[
48-
{ name: "Pentesting Security Report", link: "/pentesting/" },
49-
{ name: "Vulnerability Disclosure Process", link: "#VDP" }
48+
{ name: "Pentesting Report", link: "/pentesting/" },
49+
{ name: "Daily SBOM CVE scans", link: "/sbom/" },
50+
{ name: "Vulnerability Disclosure", link: "#VDP" }
5051
]}
5152
/>
5253

@@ -128,10 +129,17 @@ const tags = [
128129
<div slot="left">
129130
<ul>
130131
<li>As far as we know, we are <b>the only VPN solution that publishes
131-
<a href="https://defguard.net/pentesting/">detailed penetration testing reports</b>
132+
<a href="/pentesting/">detailed penetration testing reports</b>
132133
from periodic security audits</a> conducted by <a href="https://isec.pl" target="_blank">
133134
ISEC</a> on all Defguard components.
134135
</li>
136+
<li>
137+
We publish <b>Software Bill of Materials (SBOM)</b> for all our components, providing
138+
<a href="/sbom/">detailed information</a> about the ingridients of the software we ship.
139+
Every day we use the SBOMs to scan for vulnerabilities in our dependencies and publish
140+
the <a href="/sbom#sbom-list">results</a>.
141+
<b>Reacting to new vulnerabilities is a high priority for us.</b>
142+
</li>
135143
<li>
136144
Most of our code is open source, and the enterprise part is open code —
137145
enabling you to freely test and verify.

0 commit comments

Comments
 (0)