From 06a0a76b2d831e65c7b63ffa5b99c50c98871bf3 Mon Sep 17 00:00:00 2001 From: Tim Zielonko Date: Mon, 9 May 2022 12:52:52 -0500 Subject: [PATCH 1/2] port incident response use case page --- src/pages/use-cases/incident-response.tsx | 386 ++++++++++++++++++++++ 1 file changed, 386 insertions(+) create mode 100644 src/pages/use-cases/incident-response.tsx diff --git a/src/pages/use-cases/incident-response.tsx b/src/pages/use-cases/incident-response.tsx new file mode 100644 index 00000000..ed0e7a3e --- /dev/null +++ b/src/pages/use-cases/incident-response.tsx @@ -0,0 +1,386 @@ +import { FunctionComponent, ReactNode } from 'react' + +import ClockTimeThreeOutlineIcon from 'mdi-react/ClockTimeThreeOutlineIcon' +import CrosshairsGpsIcon from 'mdi-react/CrosshairsGpsIcon' +import WebIcon from 'mdi-react/WebIcon' +import Link from 'next/link' + +import { + BackButtonBold, + BlogListItem, + buttonStyle, + buttonLocation, + ContentSection, + CustomCarousel, + CustomerLogosSection, + Layout, + QuoteCarousel, + ThreeUpText, +} from '@components' + +import styles from './useCases.module.scss' + +const CarouselItem: FunctionComponent<{ header: string; text: ReactNode }> = ({ header, text }) => ( + <> +

{header}

+ {text} + +) + +const items = [ + { + buttonLabel: 'Respond to incidents faster', + text: ( + + No heroics required: Quickly understand all the context and dependencies around your codebase + with Code Search so you can find the root cause of an incident + with confidence and speed. Document work in progress with{' '} + Notebooks so teammates can get up to speed + quickly. +

+ } + /> + ), + headerClass: 'active', + itemClass: 'd-block', + }, + { + buttonLabel: 'Limit the impact of incidents', + text: ( + + Automate the deployment of fixes everywhere and at scale. With{' '} + Batch Changes, you can automate code changes and monitor the + merge status of each resulting PR. Refactor code to replace insecure functions, update + vulnerable packages, or modify container configurations across hundreds of repositories. +

+ } + /> + ), + itemClass: 'd-none', + }, + { + buttonLabel: 'Track remediation progress', + text: ( + + Visualize fixes in progress and track their deployment. With{' '} + Code Insights, get visibility into remediation efforts and + share progress with team leaders and customers. +

+ } + /> + ), + itemClass: 'd-none', + }, + { + buttonLabel: 'Monitor for the introduction of unsafe code', + text: ( + + Close the loop on your incident response efforts. After finding the root cause, use{' '} + code monitoring to track whether + similarly unsafe code is ever merged. Get alerts and stop incidents before they occur. +

+ } + /> + ), + itemClass: 'd-none', + }, +] + +const quoteCarouselItems = [ + { + header: "Quantcast is confident it won't miss any affected code", + quote: "Sourcegraph's search gave us confidence because we knew we wouldn't overlook anything: Sourcegraph returns all search results, it doesn't drop or elide them.", + by: 'Simon Law, Staff Software Engineer, Quantcast', + logoImage: '/external-logos/quantcast-logo.svg', + linkText: 'Read the case study', + link: '/case-studies/quantcast-large-scale-refactoring', + logoAlt: 'Quantcast Logo', + }, + { + header: 'Nutanix proves the Log4j vulnerability no longer affects its codebase', + quote: "Isn't it nice when you can just run a report and say, 'Here it is' or 'Here it isn't?' Much better than having to say, 'Well, boss, I think we got it all.'", + by: 'Jon Kohler, Technical Director of Solution Engineering, Nutanix', + logoImage: '/external-logos/nutanix-logo.svg', + linkText: 'Read the case study', + link: '/case-studies/nutanix-fixed-log4j-with-sourcegraph', + logoAlt: 'Nutanix Logo', + }, +] + +const resourceItems = [ + { + title: 'Log4j Log4Shell 0-day: find, fix, and track affected code', + description: + 'In the biggest security vulnerability incident since Heartbleed, Sourcegraph co-founder and CEO Quinn Slack shared how you can find affected code, automate fixes, and track progress.', + type: 'Blog post', + img: { + src: 'https://sourcegraphstatic.com/blog/log4j/log4j-blog-thumbnail.png', + alt: 'Log4j blog thumbnail', + }, + href: '/blog/log4j-log4shell-0-day', + }, + { + title: "The real weakest link in software supply chain security (it's not open source)", + description: + 'Using open source code can jump-start development but it can also expose you to security vulnerabilities. In this post, learn how to design an effective vulnerability management process that can make dependencies visible and mitigation less time-consuming.', + type: 'Blog post', + img: { + src: 'https://storage.googleapis.com/sourcegraph-assets/blog/third-party-open-source-vulnerabilities.png', + alt: 'The weakest link in software supply blog thumbnail', + }, + href: '/blog/real-weakest-link-in-software-supply-chain-security', + }, + { + title: 'How to remove secrets from your codebase', + description: + 'Back in early 2021, Sourcegraph stored infrastructure and service passwords in private repositories. Security engineer André Eleuterio moved every secret to a secure vault and used code search to ensure the move was successful and complete.', + type: 'Blog post', + img: { + src: 'https://sourcegraphstatic.com/blog/securing-sourcegraph-eliminating-secrets.png', + alt: 'Remove secrets from your codebase blog thumbnail', + }, + href: '/blog/eliminate-secrets-from-codebase-with-universal-code-search', + }, +] + +const threeUpTextItems = [ + { + icon: , + subtitle:

Assess incidents quickly

, + description: + "Pinpoint the code responsible for the incident and find the root cause in your codebase. Understand the code's functionality to verify the issue.", + }, + { + icon: , + subtitle:

Plan your remediation

, + description: + 'Reduce time to resolution by supplying response teams with actionable details, like links to all affected code.', + }, + { + icon: , + subtitle:

Execute your plan globally

, + description: + "Fix the root cause and confirm the same issue doesn't reoccur in other areas by locating the code pattern and automating fixes across your entire codebase.", + }, +] + +const IncidentResponsePage: FunctionComponent = () => ( + +
+
+
+ +

+ Resolve incidents quickly and confidently +

+
+ Identify the root cause of an incident, understand its potential impact on other + services, and fix the issue everywhere in your codebase so it won't reoccur. +
+
+ + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + + Request a demo + + + + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + + Try Sourcegraph now + + +
+
+
+
+ + } + > + + + + +
+ +
+
+

+ Incident response is stressful and overwhelming +

+

+ Current tools don't enable teams to quickly get to the root cause of an incident and ensure + it doesn't reoccur. What does that mean for you? +

+
    +
  • + Outages and degraded performance persist while development teams look for causes, + leading to lost revenue and frustrated customers. +
    • +
  • + Incidents can reoccur if developers can't find the root cause, leaving your company with + a reputation for unreliability and missed SLAs. +
    • +
  • + Incident response often relies on knowledge silos, which are neither scalable nor + sustainable. +
    • +
  • + Company leaders struggle to gain visibility into in-progress incident responses and + communicate timelines to stakeholders. +
    • +
+
+
+
+

Cloudflare quickly addresses root-cause incidents

+

+ Cloudflare engineers use Sourcegraph's code intelligence platform to refactor and debug + faster. With Sourcegraph, they can quickly identify out-of-date code libraries by only + searching certain repositories while excluding specific file types. And it's easier to + search for error logs. As a result, the team can feel confident they've addressed each + issue. +

+ + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + Read the Cloudflare case study + + Cloudflare logo +
+
+
+ +
+ + +
+
+

How Sourcegraph helps

+
+
+ +
+
+ + +
+ + + +
+ +
+ +
+
+

Get started with Sourcegraph

+

+ Respond to incidents with confidence and speed, and remediate issues at their root to ensure + they don't reoccur. +

+
+
+ + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + + Request a demo + + + + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + + Explore other use cases + + +
+
+ + +
+ +
+
+ + +
+
+

Related resources

+
+ {resourceItems.map(item => ( + + ))} +
+ + + +
+

+ Respond to incidents faster and more effectively. +

+ + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + Ready to get started? + +
+ + +) + +export default IncidentResponsePage From 298201ee068de98c1d9ccd8141b8b9ca61fb2ca0 Mon Sep 17 00:00:00 2001 From: Tim Zielonko Date: Mon, 9 May 2022 13:01:56 -0500 Subject: [PATCH 2/2] link to incident response from use cases index --- src/pages/use-cases/index.tsx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/use-cases/index.tsx b/src/pages/use-cases/index.tsx index 850e0d52..e32f0916 100644 --- a/src/pages/use-cases/index.tsx +++ b/src/pages/use-cases/index.tsx @@ -184,6 +184,10 @@ const UseCases: React.FunctionComponent = () => ( Request a demo + + {/* eslint-disable-next-line jsx-a11y/anchor-is-valid */} + Learn more +