Merge branch 'main' into docs-815-add-note-to-threatlookup-beta

Author: jpipkin1

docs/cse/records-signals-entities-insights/create-custom-entity-type.md

@@ -11,7 +11,7 @@ This topic has instructions for how to create custom entity types in Cloud SIEM.
 
 In Cloud SIEM, *entities* are fundamental to the insight generation process. When a Cloud SIEM rule fires, it generates a signal for each “on-entity” attribute configured for the rule. Cloud SIEM correlates signals by entity to create insights. This process is described in the [Insight Generation Process](/docs/cse/get-started-with-cloud-siem/insight-generation-process/) topic.
 
-Cloud SIEM has a number of built-in [entity types](/docs/cse/records-signals-entities-insights/view-manage-entities#about-entities), for example, IP Address, Hostname, and Username.
+Cloud SIEM has a number of built-in entity types, for example, IP address, hostname, and username. For a list of fields that Cloud SIEM considers entities and the entity types they map to, see [Schema: Entity Fields](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/schema/entity_fields.md) in the Cloud SIEM Content Catalog. 
 
 When you create a rule, in the signal configuration section, the rules editor prompts you to select an “on-entity” attribute from a list of all of the Cloud SIEM schema attributes that hold entities. What if you want to correlate signals by something other than an item that is one of Cloud SIEM standard entity types? That’s what custom entity types are for.
 

docs/cse/records-signals-entities-insights/view-manage-entities.md

@@ -37,29 +37,12 @@ Watch this micro lesson to learn more about entities.
 
 ## About entities
 
-In Cloud SIEM, an entity is a unique actor that a signal fired upon. Cloud SIEM has a number of [built-in entity types](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/schema/entity_fields.md):
-
-* Command
-* Deployment
-* Domain
-* Email
-* File
-* Hash
-* Hostname
-* IP Address
-* MAC Address
-* Pod
-* Process
-* Replica Set
-* Resource
-* URL
-* User Agent
-* Username
-
-You can create custom entity types as well. For more information, see [Create a Custom Entity Type](/docs/cse/records-signals-entities-insights/create-custom-entity-type/).
+In Cloud SIEM, an entity is a unique actor that a signal fired upon, for example, IP address, hostname, or username.
 
 When a signal is fired, if an entity doesn’t already exist in Cloud SIEM for the item that the signal fired on, Cloud SIEM creates an entity for it. For more information about entities and signal and insight generation, see [Insight Generation Process](/docs/cse/get-started-with-cloud-siem/insight-generation-process).
 
+For a list of fields that Cloud SIEM considers entities and the entity types they map to, see [Schema: Entity Fields](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/schema/entity_fields.md) in the Cloud SIEM Content Catalog. To create custom entity types, see [Create a Custom Entity Type](/docs/cse/records-signals-entities-insights/create-custom-entity-type/).
+
 :::note
 Entity names have a limit of 512 characters. If an entity's name value is 512 characters or longer, the system discards the log, and as a result, no signal is generated.
 :::

docs/platform-services/automation-service/app-central/integrations/incident-tools.md

@@ -7,8 +7,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/incident-tools.png')} alt="incident-tools" width="100"/>
 
-***Version: 1.8  
-Updated: June 24, 2024***
+***Version: 1.9  
+Updated: Dec 5, 2025***
 
 :::sumo Cloud SOAR
 This integration is only for Cloud SOAR.
@@ -106,3 +106,4 @@ import AccessKey from '../../../../reuse/automation-service/access-key.md';
     * Search Incidents
     * Update Entity
 * June 24, 2024 (v1.8) - The **Field ID** and **Field Value** fields are now optional in the **Update Incident Fields** action.
+* December 5, 2025 (v1.9) - Added `closing_note` in output field of Get Incident action.

docusaurus.config.js

@@ -261,8 +261,8 @@ module.exports = {
     ],
     announcementBar: {
       id: 'domain',
-      content: '🚀 <a href="https://www.sumologic.com/events/aws-reinvent">Join us at AWS re:Invent 2025 in Las Vegas, Dec 1-5</a>! Stop by Booth #1329 to see Sumo Logic Dojo AI in action and connect with our experts.',
-      backgroundColor: '#e4b0d1',
+      content: '🎉️ <b>Introducing <a href="/docs/search/mobot">Mobot</a>🤖, your conversational interface for Sumo Logic. Search logs using natural language, troubleshoot faster, and get how-to guidance.</b>',
+      backgroundColor: '#000',
       textColor: '#000',
     },
     imageZoom: {

src/css/sumo.scss

@@ -362,6 +362,17 @@ html[data-theme='light'] {
   margin-right: -10px;
 }
 
+div[class*="announcementBar_"] {
+  background: linear-gradient(
+    to right,
+    #6e9ffb 0%,
+    #91b5fc 5%,
+    #bcd2fd 8%,
+    #e1eafe 50%,
+    #bcd2fd 80%
+  ) !important;
+}
+
 .header-trial::after {
     display: none !important;
     content: none !important;