User Access Review Quarterly Recertification Evidence Tester
Flag user-access recertification rows that exceed a selected age or lack reviewer, decision, or evidence flags.
Description
Access recertification records need a reviewer, decision and supporting evidence within an explicit age allowance.
Access recertification records need a reviewer, decision and supporting evidence within an explicit age allowance. Row flags summarize already reviewed facts.1
The returned values include Evidence complete, Evidence issues, Issue row indices, Reviews checked. The How section below explains the calculation, input rules and interpretation.
When to use User Access Review Quarterly Recertification Evidence Tester
Use User Access Review Quarterly Recertification Evidence Tester when you need to evaluate the supplied records under the calculation and evidence rules below. No users, permissions or calendar dates are examined and no quarterly duration is assumed.
Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
How to use User Access Review Quarterly Recertification Evidence Tester and understand its results
- Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
- Enter maximumAgeDays, reviews using the field table and calculation rules, then run the tool.
- Read complete, issueCount, issueIndices, reviewsChecked. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| maximumAgeDays | Maximum permitted whole-day age of supporting review evidence. | integer; minimum: 0 | Required |
| reviews | Rows ordered as age in days, reviewer present, decision present, and evidence present. | list of list of number | Required |
Require nonnegative safe-integer maximum age and rows [finite nonnegative ageDays, reviewerFlag, decisionFlag, evidenceFlag]. Flags binary. Return zero-based issue indexes/count, checked count and complete when none. Empty rows returns complete; equality is permitted and fractional row ages allowed.
issue=age>maximum OR any of three flags0 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| complete | Evidence complete | boolean |
| issueCount | Evidence issues | integer; minimum: 0 |
| issueIndices | Issue row indices | list of number |
| reviewsChecked | Reviews checked | integer; minimum: 0 |
{
"input": {
"maximumAgeDays": 90,
"reviews": [
[
30,
1,
1,
1
],
[
91,
1,
1,
1
],
[
45,
1,
0,
1
]
]
},
"output": {
"complete": false,
"issueCount": 2,
"issueIndices": [
1,
2
],
"reviewsChecked": 3
}
}Limitations and assumptions
No users, permissions or calendar dates are examined and no quarterly duration is assumed.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Core numeric and string lists are limited to 100,000 entries; text entries are subject to the general large-text limit. Follow any smaller calculation limits above. Matrices are limited to 128 rows and 128 entries per row. Missing fields without a declared default, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Log Analysis User Role ITGC Sample Extraction Steps: IT general control (ITGC) log records need several source fields for follow-up testing. This check uses presence flags rather than parsing logs. For a complementary task, use Data Reliability Completeness Accuracy Source Testing Steps: Data reliability requires evidence about source, completeness, accuracy and reconciliation. Entered facts produce this transparent four-criterion screen.
References
Similar or alternative tools
- Log Analysis User Role ITGC Sample Extraction Steps
IT general control (ITGC) log records need several source fields for follow-up testing. This check uses presence flags rather than parsing logs.
- Data Reliability Completeness Accuracy Source Testing Steps
Data reliability requires evidence about source, completeness, accuracy and reconciliation. Entered facts produce this transparent four-criterion screen.