[cyera][issue] Add Cyera Issue datastream (#15107)

The PR includes issue data stream and associated dashboard. Cyera fields are mapped to their corresponding ECS fields where possible. Test samples were derived from live data samples, which were subsequently sanitized.

Author: muskan-agarwal26

packages/cyera/_dev/build/docs/README.md

@@ -8,27 +8,27 @@ The Cyera integration for Elastic allows you to collect logs and visualize the d
 
 ### Compatibility
 
-The Cyera integration supports the following versions of Cyera APIs.
+This integration is compatible with different versions of Cyera APIs for respective data streams as below:
 
 | Data streams | Version |
 |----------------|---------|
 | Classification | v1 |
 | Issue | v3 |
-| Datastore | v2 |
-| Event | v1 |
 
 ### How it works
 
-This integration periodically queries the Cyera API to retrieve classifications.
+This integration periodically queries the Cyera API to retrieve classifications and issues.
 
 ## What data does this integration collect?
 
 This integration collects log messages of the following types:
 
 - `Classification`: Collects classifications that have been identified by the Cyera system.
 
+- `Issue`: Collects issues that have been identified by the Cyera system.
+
 ### Supported use cases
-Integrating Cyera Classification data stream with Elastic SIEM provides visibility into sensitive data classification across cloud and SaaS environments. By correlating Cyera’s classification intelligence with Elastic analytics, security teams can strengthen data security posture and simplify compliance. Dashboards in Kibana present breakdowns by sensitivity, category, and trends over time, enabling faster investigations and improved accountability.
+Integrating Cyera Classification and Issues data streams with Elastic SIEM provides visibility into both sensitive data classification and the risks associated with that data across cloud and SaaS environments. By correlating Cyera’s classification intelligence with issue context in Elastic analytics, security teams can strengthen data security posture, accelerate incident response, and simplify compliance. Dashboards in Kibana present breakdowns by sensitivity, category, severity, status, risk status, and trends over time, enabling faster investigations, better prioritization, and improved accountability.
 
 ## What do I need to use this integration?
 
@@ -106,6 +106,14 @@ For more information on architectures that can be used for scaling this integrat
 
 {{event "classification"}}
 
+### Issue
+
+{{fields "issue"}}
+
+#### Example event
+
+{{event "issue"}}
+
 ### Inputs used
 
 These inputs can be used in this integration:
@@ -114,4 +122,4 @@ These inputs can be used in this integration:
 
 #### ILM Policy
 
-To facilitate classification data, source data stream-backed indices `.ds-logs-cyera.<data_stream_name>-*` are allowed to contain duplicates from each polling interval. ILM policy `logs-cyera.<data_stream_name>-default_policy` is added to these source indices, so it doesn't lead to unbounded growth. This means that in these source indices data will be deleted after `30 days` from ingested date.
+To facilitate classification and issues data, source data stream-backed indices `.ds-logs-cyera.<data_stream_name>-*` are allowed to contain duplicates from each polling interval. ILM policy `logs-cyera.<data_stream_name>-default_policy` is added to these source indices, so it doesn't lead to unbounded growth. This means that in these source indices data will be deleted after `30 days` from ingested date.