Merge pull request #11302 from harness/system-and-sto-update

[IDP] - Update : some link and YAML update of the new features

Author: ShibamD

docs/internal-developer-portal/catalog/system-entity.md

@@ -43,8 +43,8 @@ Use Systems to:
 In Harness IDP, a **System** represents a logical grouping of related services, APIs, and resources. Systems help improve catalog visibility, support governance across scopes, and make it easier for teams to discover and manage what they own.
 
 Systems can be created through:
-- The **Harness UI/YAML** view
-- The **Create Entity API** by mentioning the `kind: System`
+- The **[Harness UI](/docs/internal-developer-portal/catalog/manage-catalog#harness-idp-ui)** or **[YAML](/docs/internal-developer-portal/catalog/manage-catalog#catalog-yaml)** view
+- The **[Create Entity API](https://apidocs.harness.io/tag/Entities#operation/create-entity)** by mentioning the `kind: System`
 
 They can exist at **Project**, **Organization**, or **Account** scope, based on how broadly you want to apply grouping logic.
 
@@ -105,7 +105,7 @@ We can edit the **System Layout** under `Admin → Layout → Catalog Entities 
 
 
 
-The configuration is defined in YAML, for example:
+#### The configuration is defined in YAML, for example:
 
 ```yaml
 page:
@@ -123,6 +123,7 @@ page:
               variant: gridItem
             gridProps:
               md: 6
+              // highlight-start
         - component: EntityCatalogGraphCard
           specs:
             props:
@@ -131,11 +132,11 @@ page:
             gridProps:
               md: 6
               xs: 12
+        // highlight-end
         - component: EntityScoreCard
           specs:
             gridProps:
               md: 6
-        // highlight-start
         - component: EntityLinksCard
           specs:
             props:
@@ -144,7 +145,6 @@ page:
             gridProps:
               md: 6
               xs: 12
-        // highlight-end
         - component: CatalogTable
           specs:
             props:

docs/internal-developer-portal/plugins/available-plugins/harness-native-plugins/sto-integration.md

@@ -304,6 +304,25 @@ Here, you will see:
 
 This view bridges the gap between high-level visibility and actionable insight.
 
+#### How to Add or Remove the STO Vulnerabilities Card
+
+You can customize whether the STO Vulnerabilities card appears on the entity overview page by modifying the layout configuration in the IDP admin UI.
+
+Navigate to **Layout**, then select the appropriate entity kind (e.g., `component`) and entity type (e.g., `service`). Here, you can add or remove the STO Vulnerabilities card component for the overview tab.
+
+To **add** the STO Vulnerabilities card, include the following in your layout YAML:
+
+```yaml
+        - component: EntitySecurityIssueCard
+          specs:
+            props:
+              variant: gridItem
+              height: 400
+            gridProps:
+              md: 6
+              xs: 12
+```
+
 <DocImage path={require('./static/sto-vul-summary.png')} />
 
 ### Vulnerabilities Tab of Entity View
@@ -344,6 +363,57 @@ To **remove** the tab, simply delete or comment out this section from the layout
 
 The highlighted section in the image above shows the configuration for the Vulnerabilities tab. Once added, developers will see a dedicated tab for STO security findings directly on each service's entity page, making it easy to review and act on vulnerabilities in context.
 
+
+<details>
+<summary>Sample Catalog Layout YAML</summary>
+
+```yaml
+page:
+  name: EntityLayout
+  tabs:
+    - name: Overview
+      path: /
+      title: Overview
+      contents:
+        - component: EntityOrphanWarning
+        - component: EntityRelationWarning
+        - component: EntityProcessingErrorsPanel
+        - component: EntityAboutCard
+          specs:
+            props:
+              variant: gridItem
+            gridProps:
+              md: 6
+        - component: EntityScoreCard
+          specs:
+            gridProps:
+              md: 6
+        - component: EntityCatalogGraphCard
+          specs:
+            props:
+              variant: gridItem
+              height: 400
+            gridProps:
+              md: 6
+              xs: 12
+// highlight-start
+        - component: EntitySecurityIssueCard
+          specs:
+            props:
+              variant: gridItem
+              height: 400
+            gridProps:
+              md: 6
+              xs: 12
+    - name: EntitySecurityIssueContent
+      path: /security
+      title: Vulnerabilities
+      contents:
+        - component: EntitySecurityIssueContent
+// highlight-end
+```
+</details>
+
 ## Scorecards – Measuring Vulnerability
 
 Harness IDP Scorecards let you track your security posture automatically, using data from STO scans. You can set up custom vulnerability checks—like thresholds on critical vulnerabilities—and see compliance at a glance for all your services.

release-notes/internal-developer-portal.md

@@ -72,7 +72,7 @@ Harness Internal Developer Portal (IDP) now supports System as a high-level cata
 
 * Systems can be created at Account, Organization, or Project scope.
 * Define Systems using the IDP UI, YAML, or the Create Entity API (`kind: System`).
-* New default System layout includes tabs for Overview, Entities, Scorecard, and Diagram. Existing customers can apply the provided YAML layout under **Admin → Layout → Catalog Entities → System**.
+* New default System layout includes tabs for Overview, Entities, Scorecard, and Diagram. Existing customers can apply the provided [YAML layout](/docs/internal-developer-portal/catalog/system-entity#the-configuration-is-defined-in-yaml-for-example) under **Admin → Layout → Catalog Entities → System**.
 ![](./static/system-layout.png)
 * The Entities tab offers a searchable, filterable, and sortable table of all Components, APIs, and Resources within the System.
 * Many-to-many relationships are supported — an entity can belong to multiple Systems.
@@ -118,6 +118,8 @@ metadata:
     - java
 ```
 
+Learn more about [System Entity](/docs/internal-developer-portal/catalog/system-entity)
+
 ### [New Feature] Link to Source Code Repository
 
 Harness IDP now supports defining a Link to Source Code Repository for Components, APIs, and Resources in the Software Catalog. This optional field is strongly recommended for Git-based workflows and enables key capabilities such as: