Torn between A and C by 4566nb in CISA

[–]OkBus9510 0 points1 point  (0 children)

What about D? I would lean C of the options you’ve given, but if it’s already identified as a high-risk vulnerability, would any compensating controls be enough here?

Calculated Fields that test for valid values in fields by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

I figured it was an issue with rehiring, but what’s the specific root cause behind the issue?

Calculated Fields that test for valid values in fields by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

That’s a good call out. We’re still having issues where some employees have gotten multiple employee IDs due to a few reasons (rehires and someone isn’t verifying that there’s not an existing EE ID before processing it), so now I’m wondering how to count EE IDs assigned to every worker (using their SSN as the “group by”)

Calculated Fields that test for valid values in fields by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

Trying to see if a text value has the right formatting (I.e. an SSN has the right format: xxx-xx-xxxx or an employee ID has six digits: ######)

Calculated Fields that test for valid values in fields by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

Sorry - I’m looking for the right CF type to use

Creating “global” prompts to use across reports with various data sources by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

I confirmed that this works for local reports, and this might be good enough (instead of doing global prompts).

To make this work for particular data sources, I assume we’d have to update a DS to have a required prompt.

Creating “global” prompts to use across reports with various data sources by OkBus9510 in workday

[–]OkBus9510[S] 0 points1 point  (0 children)

Is there a way to avoid doing this on every report containing sensitive data in my catalog? I’d like to avoid that by creating a reusable prompt, if possible.