Posture Analytics - Security Transitions
Posture Analytics provides change-driven threat detection. Where the K8 Data Security topology shows what your storage looks like now, this page shows what changed and whether the change is a threat.
The platform keeps a history for every scan: PII classifications, language-coherence (LC) integrity scores, pod, PVC, and bucket inventory snapshots, and audit throughput. The latest value alone, such as "this file has PII count 12, LC 0.82", hides the security signal. The signal is usually in the transition from one state to another. Examples include:
- A file that changes from clean to PII, which means sensitive data was written where it should not be.
- A file that changes from coherent to gibberish. A sharp LC drop with an entropy spike and a changed content hash is the pattern of ransomware encrypting in place, corruption, or steganographic exfiltration.
- A throughput spike at 2 a.m. on a Sunday against a quiet weekend baseline, which can indicate exfiltration staging.
The page shows these transitions as a live feed, scores them, and lets you triage them.
Transitions feed
The transitions feed lists detected changes, newest first. Each row describes one transition rather than one raw value. For example:
PII 0 → 12 (new: SSN)— a file that was clean now has 12 PII entities, including a new entity type (SSN).LC 0.82 → 0.21 ⚠ gibberish— language coherence collapsed because the file's bytes changed. This is the main ransomware and integrity signal.
Each row contains the following fields.
| Field | Description |
|---|---|
| Signal | The detector that fired. See Signals. |
| Entity | The file, pod, PVC, or bucket where the transition was observed, with its namespace. |
| From → To | The state before and after, for example clean → pii, 0.82 → 0.21, or absent → present. |
| Severity | INFO, LOW, MEDIUM, HIGH, or CRITICAL. |
| Confidence | A value from 0 to 1 that reflects how strong the evidence for the transition is. |
| Evidence | The rows that contributed, and a sparkline of the metric's recent trend for the file. |
Signals
| Signal | Description |
|---|---|
pii | A change in PII classification. |
lc | A sharp content-integrity drop. See LC and LC drift. |
lc_drift | A slow content-integrity drift. See LC and LC drift. |
throughput | A throughput spike against the work-zone baseline. See Throughput anomalies. |
data_security_event | A single summary of failed audit events from the last 24 hours. See Data Security Event. |
Trino (structured) | A filter group for all Trino SQL behavioral anomalies. See Trino (structured) filter group. |
The signal filter also lists ephemeral, access, cve, and correlated. These signals are not produced in this release, so filtering on them shows no rows.
LC and LC drift
lc— a sharp content-integrity drop. In a single scan, a file's bytes changed and its coherence collapsed. This is the main ransomware signal.lc_drift(shown as LC Drift) — a slow drift. The file's recent-weighted coherence and entropy gradually move into the concerning range through many small changes that never trigger the sharp detector. This is a low-severity early warning. It is never higher than MEDIUM and does not raise an alarm by itself. Treat it as a prompt to watch the file.
Trino (structured) filter group
Trino (structured) is a filter group, not a single detector. Selecting it limits the feed to all Structured Anomaly Detection signals so you can see every Trino SQL behavioral anomaly together. These signals are:
trino_volumetrino_write_surgetrino_destructiontrino_novel_accesstrino_rare_accesstrino_opmix_shifttrino_peer_outliertrino_failed_probetrino_table_anomaly
Each card still shows its specific trino_<signal> label. For the learned baselines behind these signals, see Structured Behavioral Baselines.
Data Security Event
data_security_event is a single summary card that covers every failed audit event in the last 24 hours across PowerScale (Dell OneFS) file storage and ObjectScale (Dell ECS) object storage. There is one card, not one row per failure.
- Collapsed view — a line such as "N failed audit events across E workloads, last 24h".
- Expanded view — a tree of cluster, pod, PVC or bucket, and error code with its count. It shows which pods are hitting permission errors, credential failures, or probing patterns, and on which volume or bucket.
- Included entities — only PVCs and buckets that are mapped to a pod. Unmapped volumes are excluded.
- Error codes — the raw audit failure reason, for example
failure(0xC0000022)orfailure(403). - Severity — audit failures are common, so severity is capped at MEDIUM and the card never raises an alarm by itself. Treat it as a signal to investigate.
- Refresh — the card updates about every 30 minutes with the latest 24-hour picture. It disappears when failures stop, so an empty feed means there are no recent failures in the fleet.
Read a transition
- Check severity, then confidence. A
CRITICALrow with high confidence needs action. A singleLOWorINFOtransition is usually informational and may be a statistical fluctuation. - Check the direction.
clean → piiandcoherent → gibberishare degradations. The feed shows changes so you can see degradations without reading absolute scores. - Open the row for evidence. The row expands to show before and after details and the metric sparkline.
- Check the entity. Note the entity and its namespace, then look it up in the K8 Data Security topology and in Data Auditing to see what else the pod, PVC, or bucket did around the same time.
Severity
Each transition is scored on its own signal. Signals on the same entity are not combined into one row. A single change can be HIGH or CRITICAL: for example, a file that changes from clean to PII is HIGH, and CRITICAL when the new PII includes a sensitive type.
Baselines need history. On a new deployment, the lc_drift and throughput detectors wait until enough samples accumulate before they score. The pii and lc detectors report from the first scans.
Acknowledge and suppress
Statistical detection produces some false positives, so you can triage every transition.
- Ack — marks the transition as reviewed. Use it after you investigate a row and decide what to do. The transition still contributes to history, and the action records that a person has seen it.
- Suppress — marks the transition as a known false positive. Use it for expected behavior in your environment, such as a routine nightly batch job that moves large volumes off-hours. Suppressed transitions are kept for audit, but they leave the active triage view.
These are operator controls. They change how a transition is shown and weighted, not the underlying detection, and they do not delete the record.
Throughput anomalies
The throughput section below the feed uses the audit stream's byte counters to detect exfiltration and ransomware. It has an anomaly table that lists what to act on, and a set of graphs per storage device that gives the overall picture. There are no per-PVC or per-bucket graphs. The table identifies the specific entities.
Work-zone baselines
Throughput is scored against a work-zone baseline, not a single global average. Each hour is compared with its own time-of-day band.
| Zone | Hours |
|---|---|
| Working hours | 09:00–17:00, Monday to Friday |
| After hours | Outside 09:00–17:00, Monday to Friday |
| Weekends | All day, Saturday and Sunday |
Zones are computed in UTC, so working hours are 09:00–17:00 UTC. A value is anomalous when it exceeds the upper limit of its zone's band, which is the mean plus three standard deviations.
- A large read or get spike on a weekend, far above that zone's quiet baseline, is the pattern of data exfiltration.
- A large off-hours write or put spike is the pattern of ransomware staging.
A single global baseline would hide a quiet-weekend spike under the busy weekday average and flag normal weekday activity as anomalous. Work zones avoid both problems.
Anomaly table
The table lists the PVCs and buckets whose throughput crossed their work-zone band in the last 30 days. This is the same window as the device graphs, so the table names the entities behind the crossings you see in the graphs.
- Rows are ranked by severity, and each row lists the pods that use the PVC or bucket.
- Use the Min severity filter to focus on what meets your threshold, for example HIGH and above.
- Each row shows the zone and direction, the peak rate in the window compared with the band, the z-score (standard deviations above normal), the number of hourly buckets that crossed the band, and when it was last seen.
- Sustained current spikes also appear as
throughputrows in the transitions feed. They raise an alarm when severity is high. The Alarms page is not available in this release. - An empty table means every monitored PVC and bucket stayed within its bands during the window.
Device graphs
Each storage device (PowerScale cluster or ObjectScale device) has one graph. It shows the device's total bytes per second over the last 30 days as a line, over its work-zone baseline band as a dashed line. Red dots mark where the device as a whole exceeded its expected band.
Use the graphs to check whether anything is unusual across a device. Then use the anomaly table to find the PVC, bucket, and pods responsible.
A new entity or zone with too few samples is not scored until enough buckets accumulate. This avoids false positives at startup.
Triage
Acknowledging or suppressing a transition is a triage action on the feed.
Tips
- The
lcgibberish signal, a sharp coherence drop with an entropy spike and a changed content hash, is the strongest single ransomware indicator. Treat aCRITICALlcrow as a priority. - A
throughputtransition is meaningful relative to its own work-zone baseline. A large read at 2 p.m. on a Tuesday is normal, but at 2 a.m. on a Sunday it is anomalous. The feed already scores against the matching zone, so rely on the severity rather than the raw byte count. - Use Suppress sparingly. Over-suppressing hides real changes. Use Ack for "seen, benign this time", and use Suppress only for recurring expected behavior.
Common workflows
Triage the day's transitions
- Open Posture Analytics and read the feed from the top, newest first.
- Filter to
CRITICAL, then toHIGH, to focus on the most important rows. The severity filter shows one exact severity at a time. - Open each high-severity row, read its evidence and sparkline, and look up the entity in the K8 Data Security topology or in Data Auditing to confirm.
- Click Ack on the rows you have reviewed. Suppress any that are confirmed expected behavior.
Investigate a suspected ransomware event
- Filter the feed to the
lcsignal. - Look for
coherent → gibberishtransitions, which are a sharp LC drop with a content-hash change. - Open the row and review its evidence and sparkline. Check the throughput anomalies for off-hours activity on the same PVC or bucket.
- Look up the affected PVC or pod in the K8 Data Security topology and in Data Auditing to determine the scope.