+ {subtitle} +
+ ) : null}
- Containers don't get built from scratch, they inherit layers of open source
- packages, base images, and dependencies. Most organizations have no clear view into
- what vulnerabilities came along for the ride, where they're running, or who's
- responsible for fixing them.
+
+ Containers are assembled from base images, open source packages and dependencies, each + with its own layers. A vulnerability can arrive through any of them, which makes it + hard to know what you’re actually running. +
++ Black October showed how that plays out:
-- Knowing you have vulnerable containers is not the same as being able to do something - about it. Many organizations have invested heavily in visibility tooling only to find - themselves with dashboards full of findings and no clear path to resolution. -
- Security teams need more than a list. They need{" "} - remediation guidance, specific, - prioritized actions that tell them which vulnerable containers to remove first, how to - reduce exposure quickly, and how to fix it. Without that, findings pile up, fatigue - sets in, and real risk goes unaddressed. + Finding these by hand means checking every image, in every environment, one at a time.
-{title}
++ {detail} +
+{term}
++ {detail} +
++ {answer} +
++ {detail} +
+
-
- {/* Ellipse glow — top-left. */}
-
-
-
- {/* Ellipse glow — bottom-right. */}
-
-
-
- {/* Decorative violet cube — bottom-RIGHT corner. It used to sit
- bottom-left, where it ran under the headline's last line. The right
- side of the card is clear below the button, so the cube reads as
- decoration there instead of as something behind the text. */}
- {/* eslint-disable-next-line @next/next/no-img-element */}
- 
-
- {/* Smaller cube for the stacked layout. `lg:hidden` rather than
- `md:hidden`: the large cube above is `lg:block`, so gating this one at
- md left 768-1023px with no cube at all. */}
- {/* eslint-disable-next-line @next/next/no-img-element */}
-
-
- {/*
- * One content block across all widths, on the same grid LibrariesCTA and
- * the other product CTAs use: stacked and centred below lg, two columns
- * above it.
- *
- * `lg:items-start` is the point of the grid. The previous flex row centred
- * each column on its own axis, and the right column is taller (three lines
- * plus a button), so the headline settled below the supporting line's
- * first line and the two read as misaligned. Top-aligning the columns and
- * centring the grid as a whole (`lg:content-center`) puts their first
- * lines on one baseline.
- *
- * This also replaces a duplicated mobile block that repeated the headline,
- * description and button in the DOM at every width.
- */}
- - {HEADLINE} -
-- {DESCRIPTION} -
- - - {BUTTON_LABEL} - -- See your risks. Get expert insights. Take action with confidence. + Know where you’re affected, what’s running in production, and what to do next.
+
+ {/* Ellipse glow, top-left. */}
+
+
+
+ {/* Ellipse glow, bottom-right. */}
+
+
+
+ {/* Decorative violet cube, bottom-RIGHT corner. It used to sit
+ bottom-left, where it ran under the headline's last line. The right
+ side of the card is clear below the button, so the cube reads as
+ decoration there instead of as something behind the text. */}
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+
+ {/* Smaller cube for the stacked layout. `lg:hidden` rather than
+ `md:hidden`: the large cube above is `lg:block`, so gating this one at
+ md left 768-1023px with no cube at all. */}
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+
+ {/*
+ * One content block across all widths, on the same grid LibrariesCTA and
+ * the other product CTAs use: stacked and centred below lg, two columns
+ * above it.
+ *
+ * `lg:items-start` is the point of the grid. The previous flex row centred
+ * each column on its own axis, and the right column is taller (three lines
+ * plus a button), so the headline settled below the supporting line's
+ * first line and the two read as misaligned. Top-aligning the columns and
+ * centring the grid as a whole (`lg:content-center`) puts their first
+ * lines on one baseline.
+ *
+ * This also replaces a duplicated mobile block that repeated the headline,
+ * description and button in the DOM at every width.
+ */}
+ + {headline} +
++ {description} +
+ + + {buttonLabel} + +- {ABOUT_CLEANSTART.body} -
- + {/* Stage light behind the panel, and a faint dot grid that fades out from it. */} + + + ++ {ABOUT_CLEANSTART.body} +
+ +- {paragraph} -
- ))} -+ {paragraph} +
+ ))} ++ {paragraph} +
+ ))} +- {paragraph} + {reference.publisher}
- ))} -- {reference.publisher} -
-- {reference.title} -
-+ {reference.title} +
+ + ))} + +- {HERO.eyebrow} -
-
- - {DOWNLOAD.body} -
-+ {lead} {rest} +
+- {lead} -
-- {paragraph} -
- ))} -+ {part.lead} {part.rest} +
+ ); + })} +
-
-
- {vulnerabilities.caption} -
-
+
+
+ {vulnerabilities.caption} +
-
- {components.caption} -
+ {/* Estate size, split by how a component got there. */} +
+
+ {components.caption} +
+
+
- {age.caption}
-
+ {age.caption}
+
+
+
+
+
-
-
- {malicious.caption} -
-
+
+ {malicious.caption} +
+
-
- {ai.caption} -
+
+
+ {ai.caption} +
-
+ {second}
- {`“${first}`} {`${second}”`}
- {LEADERSHIP.name}
-
- {LEADERSHIP.role}
-
+
+ “
+
+
-
- {LEADERSHIP.label}
-
-
+
- {LEADERSHIP.heading}
-
+ ”
+
+ {first}
+
+
-
+ {LEADERSHIP.role} +
+{DOWNLOAD.heading}
+{DOWNLOAD.body}
++ {DOWNLOAD.heading} +
+{DOWNLOAD.body}
++ {paragraph.map((run) => + typeof run === "string" ? ( + run + ) : ( + + {run.strong} + + ), + )} +
+ ))} +- {finding.number} -
-- {paragraph.map((run) => - typeof run === 'string' ? ( - run - ) : ( - {run.strong} - ), - )} -
- ))} -
+
-
- {/* Ellipse glow — top-left. */}
-
-
-
- {/* Ellipse glow — bottom-right. */}
-
-
-
- {/* Decorative violet cube — bottom-RIGHT corner. It used to sit
- bottom-left, where it ran under the headline's last line. The right
- side of the card is clear below the button, so the cube reads as
- decoration there instead of as something behind the text. */}
- {/* eslint-disable-next-line @next/next/no-img-element */}
-
-
- {/* Smaller cube for the stacked layout. `lg:hidden` rather than
- `md:hidden`: the large cube above is `lg:block`, so gating this one at
- md left 768-1023px with no cube at all. */}
- {/* eslint-disable-next-line @next/next/no-img-element */}
-
-
- {/*
- * One content block across all widths, on the same grid LibrariesCTA and
- * the other product CTAs use: stacked and centred below lg, two columns
- * above it.
- *
- * `lg:items-start` is the point of the grid. The previous flex row centred
- * each column on its own axis, and the right column is taller (three lines
- * plus a button), so the headline settled below the supporting line's
- * first line and the two read as misaligned. Top-aligning the columns and
- * centring the grid as a whole (`lg:content-center`) puts their first
- * lines on one baseline.
- *
- * This also replaces a duplicated mobile block that repeated the headline,
- * description and button in the DOM at every width.
- */}
- - {HEADLINE} -
-- {DESCRIPTION} -
- - - {BUTTON_LABEL} - -+ Secure your telecommunications infrastructure with visibility, hardened images and + verified software dependencies. +
++ {p.tagline} +
+ + Explore {p.name} +
+
+ + {step.body} +
++ {s.body} +
+
+ );
+}
+
+function OutcomeFigure({ Icon, line1, line2, body }: Outcome): React.ReactElement {
+ return (
+ + {body} +
+
+ 
+ 
+
+ + {p.body} +
+
+
+ + Every software component powering your network can introduce risk. +
++ {body} +
+