Skip to content

Commit 5154812

Browse files
Merge pull request #46 from funnelfiasco/issue22-improve_messaging
Improve messaging/positioning of GUAC
2 parents cff7e39 + 2cb1557 commit 5154812

File tree

3 files changed

+61
-6
lines changed

3 files changed

+61
-6
lines changed

config.yaml

+3-5
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ params:
4343
subtitle: GUAC gives you directed, actionable insights into the security of your software supply chain.
4444
# Button text
4545
button1text: Find out more
46-
button1link: "#problem"
46+
button1link: "/why-guac"
4747
button2text: Try it out
4848
button2link: "https://docs.guac.sh/getting-started/"
4949
button3text: Now an OpenSSF incubating project!
@@ -63,6 +63,8 @@ params:
6363
# - gutwork
6464
# Customizable navbar. For a dropdown, add a "sublinks" list.
6565
navbar:
66+
- title: Why GUAC?
67+
url: /why-guac
6668
- title: Community
6769
url: /community
6870
- title: Blogs
@@ -201,10 +203,6 @@ params:
201203
button2Text: Demos
202204
button2Link: https://docs.guac.sh/guac-use-cases/
203205

204-
sectionProblem:
205-
title: The current problem with software supply chain security
206-
subtitle: Software supply chain attacks are on the rise and it’s hard to know what your software is at risk for and how to protect it. Many tools are available to help you generate Software Bills of Materials (SBOMs), signed attestations, and vulnerability reports, but they stop there, leaving you to figure out how they all fit together.
207-
208206
sectionVision:
209207
title: Our Vision
210208
subtitle: GUAC (Graph for Understanding Artifact Composition) aims to fill in the gaps by ingesting software metadata, like SBOMs, and mapping out relationships between software. When you know how one piece of software affects another, you’ll be able to fully understand your software security position and act as needed.

content/why-guac.md

+57
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: "Why GUAC?"
3+
section: single
4+
type: page
5+
include_footer: true
6+
---
7+
8+
## The current problem with software supply chain security
9+
10+
Software supply chain attacks are on the rise and it’s hard to know what your software is at risk for and how to protect it.
11+
Many tools are available to help you generate software bills of materials (SBOMs), signed attestations, and vulnerability reports, but they stop there, leaving you to figure out how they all fit together.
12+
GUAC provides an aggregated, queryable view across your whole software supply chain, not just one SBOM at a time.
13+
14+
## From data to knowledge
15+
16+
Consider the [DIKW pyramid](https://en.wikipedia.org/wiki/DIKW_pyramid).
17+
You have *data* about your software supply chain in the form of SBOMs, vulnerability statements, and the like.
18+
GUAC builds a graph of the relationships between the data in order to provide *information*.
19+
With GUAC, you can ask questions of your supply chain relationships to get *knowledge*.
20+
By ingesting local information and trusted third-party sources, GUAC gives you the ability to perform a comprehensive analysis.
21+
22+
## Use cases
23+
24+
GUAC is for developers, operations, and security practitioners who need to identify and address problems in their software supply chain, including proactively managing dependencies and responding to vulnerabilities.
25+
GUAC provides supply chain observability with a graph view of the software supply chain and tools for performing queries to gain actionable insights.
26+
27+
Here are some common use cases for GUAC.
28+
[Let us know](/community) yours.
29+
30+
### Developers
31+
32+
* Identify deprecated and unsupported dependencies
33+
* Discover “version sprawl”, where several versions of the same dependency are included
34+
* Locate and remediate vulnerable dependencies
35+
* Identify risky upstreams based on security practices evaluated by OpenSSF Scorecard
36+
37+
### Operations engineers
38+
39+
* Locate and remediate vulnerable dependencies
40+
41+
### Security engineers
42+
43+
* Locate and remediate vulnerable dependencies
44+
* Prevent known vulnerable packages and sources from being used in applications
45+
46+
### Open Source Program Offices
47+
48+
* Identify strategically important open source upstreams
49+
* Identify open source upstreams that could benefit from security help based on OpenSSF Scorecard results
50+
51+
## Differentiation
52+
53+
GUAC has three key differentiating features from other tools in this space
54+
55+
* **Works on more than one SBOM at a time.** This allows observability into the entire software portfolio instead of application-by-application.
56+
* **Aggregates additional data beyond the SBOM.** GUAC brings in data like dependencies and vulnerabilities from trusted third-party sources, enriching the supply chain graph.
57+
* **Provides APIs and a visualization tool.** GUAC’s query and visualization tooling let the user get the answers to the questions they need to ask.

themes/hugo-fresh/layouts/partials/section1.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
{{- $title := index $section1 "title" }}
33
{{- $subtitle := index $section1 "subtitle" }}
44
{{- $tiles := index $section1 "tiles" }}
5-
<section class="section section-secondary is-medium">
5+
<section class="section section-quad is-medium">
66
<div class="container">
77
<div class="title-wrapper has-text-centered">
88
<h2 class="title is-2 light-text">{{ $title }}</h2>

0 commit comments

Comments
 (0)