diff --git a/articles/linux-vulnerability-detection-with-oval-and-fleet.md b/articles/linux-vulnerability-detection-with-oval-and-fleet.md index c86ac9b636..9c645b50c1 100644 --- a/articles/linux-vulnerability-detection-with-oval-and-fleet.md +++ b/articles/linux-vulnerability-detection-with-oval-and-fleet.md @@ -14,7 +14,18 @@ The availability of OVAL definitions varies depending on the target OS. Still, l We’ll go into more detail about how we use OVAL for detecting software vulnerabilities on the most popular distros (Ubuntu, CentOS, Fedora, and RedHat). But first, let’s look at the vulnerability detection pipeline from a bird’s-eye view. -![Linux vulnerability detection with OVAL and Fleet diagram](../website/assets/images/articles/linux-vulnerability-detection-diagram.jpg) +```mermaid +flowchart TD + A[Determine OVAL definition URL for OS] --> B{Already downloaded?} + B -->|Yes| C{Up to date} + B -->|No| D[Download definition] + D --> E[Parce definition] + C -->|Yes| F[Analyze software inventory] + C -->|No| G[Remove old definition] + G --> D + F --> I[Report findings] + E --> F +``` ## Determining what OVAL definitions to download @@ -68,6 +79,6 @@ Once all vulnerabilities are collected, we synchronize the results with what we - + diff --git a/website/assets/styles/pages/articles/basic-article.less b/website/assets/styles/pages/articles/basic-article.less index f1e1c7645d..091d09d6d9 100644 --- a/website/assets/styles/pages/articles/basic-article.less +++ b/website/assets/styles/pages/articles/basic-article.less @@ -131,6 +131,7 @@ display: inline-block; margin-left: auto; margin-right: auto; + background: #fff; } blockquote { margin: 16px 0 32px;