ITGC Access Change Operations Domain Split Lookup
Split labeled controls across access, change, and operations ITGC domains and report missing domains and malformed mappings.
Description
ITGC coverage can be organized into access, change and operations domains.
ITGC coverage can be organized into access, change and operations domains. A mapping label records scope rather than testing its controls.1
The returned values include All domains covered, Covered domains, Missing domains, Unmapped controls. The How section below explains the calculation, input rules and interpretation.
When to use ITGC Access Change Operations Domain Split Lookup
Use ITGC Access Change Operations Domain Split Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. Complete can coexist with unmapped controls. No domain definitions, actual controls or effectiveness are inferred.
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 ITGC Access Change Operations Domain Split Lookup 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 domainControls using the field table and calculation rules, then run the tool.
- Read complete, coveredDomains, missingDomains, unmappedControls. 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 |
|---|---|---|---|
| domainControls | Control labels in domain:control form, such as access:user review. | list of string | Required |
Supply possibly empty domain:control strings. Require a colon; trim/lowercase prefix and retain nonblank remainder as detail. Unknown domains or blank details are returned as unmapped; valid prefixes contribute coverage. Return covered/missing domains in access/change/operations order and complete flag.
complete=all three domains represented Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| complete | All domains covered | boolean |
| coveredDomains | Covered domains | list of string |
| missingDomains | Missing domains | list of string |
| unmappedControls | Unmapped controls | list of string |
{
"input": {
"domainControls": [
"access: quarterly user review",
"change: emergency change approval",
"unknown: orphaned control"
]
},
"output": {
"complete": false,
"coveredDomains": [
"access",
"change"
],
"missingDomains": [
"operations"
],
"unmappedControls": [
"unknown: orphaned control"
]
}
} Limitations and assumptions
Complete can coexist with unmapped controls. No domain definitions, actual controls or effectiveness are inferred.
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. 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 User Access Review Quarterly Recertification Evidence Tester: Access recertification records need a reviewer, decision and supporting evidence within an explicit age allowance. Row flags summarize already reviewed facts.
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.
- User Access Review Quarterly Recertification Evidence Tester
Access recertification records need a reviewer, decision and supporting evidence within an explicit age allowance. Row flags summarize already reviewed facts.