Cookies & analytics

    We use cookies for analytics and to serve ads. Accept to enable Google Analytics and AdSense. You can decline to stay opt-out.

    SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact
      Stack

      Security Advisory Stack

      Security advisories with Article + SoftwareApplication context, FAQs, and breadcrumb navigation.

      Open generatorValidate in Rich Results Test

      When to use this stack

      • Security vulnerability advisories tied to a product or app
      • CVE-style posts that need affected product/version context
      • Pages where FAQs address impact, remediation, and timeline

      What's included

      • Represents the advisory content with headline, dates, and author/publisher.

      • Software App
        Open generator

        Anchors the affected product/application with version details.

      • Frequently Asked Questions
        Open generator

        Answers remediation, impact, and upgrade guidance.

      • Breadcrumb
        Open generator

        Provides navigation context from the security hub.

      Required properties (stack union)

      Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

      applicationCategory
      author.name
      datePublished
      description
      headline
      itemListElement[].name
      mainEntity[].@type=Question
      mainEntity[].acceptedAnswer.text
      name
      operatingSystem
      url

      Recommended properties (stack union)

      about.@id
      dateModified
      inLanguage
      itemListElement[].item
      mainEntity[].acceptedAnswer.text
      mainEntity[].author.name
      mainEntity[].name
      offers.url
      publisher.name
      softwareVersion
      url

      Combined JSON-LD

      Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the page.

      Validate
      [
        {
          "@context": "https://schema.org",
          "@type": "Article",
          "@id": "https://www.example.com/security/advisories/2025-01-sso-bypass#article",
          "headline": "Security Advisory: SSO Bypass in Legacy SAML Flow",
          "description": "We identified and fixed an SSO bypass affecting legacy SAML configs. Update to v5.12.3 or apply the mitigation.",
          "datePublished": "2025-01-20",
          "dateModified": "2025-01-21",
          "inLanguage": "en",
          "url": "https://www.example.com/security/advisories/2025-01-sso-bypass",
          "author": { "@type": "Organization", "name": "Example Security Team" },
          "publisher": { "@type": "Organization", "name": "Example Corp" },
          "about": { "@id": "https://www.example.com/security/advisories/2025-01-sso-bypass#app" }
        },
        {
          "@context": "https://schema.org",
          "@type": "SoftwareApplication",
          "@id": "https://www.example.com/security/advisories/2025-01-sso-bypass#app",
          "name": "Example Identity Suite",
          "applicationCategory": "Security",
          "operatingSystem": "SaaS",
          "softwareVersion": "5.12.2",
          "offers": {
            "@type": "Offer",
            "url": "https://www.example.com/security/releases/5.12.3"
          }
        },
        {
          "@context": "https://schema.org",
          "@type": "FAQPage",
          "mainEntity": [
            {
              "@type": "Question",
              "name": "Which versions are affected?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "Versions 5.10.0 through 5.12.2 with legacy SAML enabled are affected. Versions 5.12.3+ are patched."
              }
            },
            {
              "@type": "Question",
              "name": "What is the fix?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "Upgrade to 5.12.3 or later. As a temporary mitigation, disable legacy SAML and enforce modern SSO policies."
              }
            },
            {
              "@type": "Question",
              "name": "Is there any evidence of exploitation?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "We have no evidence of exploitation. Logs and IDS rules have been updated to detect attempts. Contact security@example.com with questions."
              }
            }
          ]
        },
        {
          "@context": "https://schema.org",
          "@type": "BreadcrumbList",
          "itemListElement": [
            { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
            { "@type": "ListItem", "position": 2, "name": "Security Advisories", "item": "https://www.example.com/security/advisories" },
            { "@type": "ListItem", "position": 3, "name": "SSO Bypass (2025-01)", "item": "https://www.example.com/security/advisories/2025-01-sso-bypass" }
          ]
        }
      ]

      Implementation steps

      1. Start from your live product detail page content; ensure titles, prices, and availability match the page.
      2. Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
      3. Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
      4. Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
      5. Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
      6. Validate in the Rich Results Test and revalidate after price/availability/policy changes.

      Common errors and fixes

      FAQs

      Should I include CVE IDs?

      Include the CVE in the Article body and headline if assigned. Keep JSON-LD aligned with what’s visible on the page.

      How do I show multiple affected products?

      Add one SoftwareApplication object per affected product/version and link them from the Article via about.@id.

      References