Trust, with a basis.
Control mapping, customer assurance, procurement responses and processor governance.
Domains 1, 4, 8, 9
Technology risk · GRC · AI governance
Controls you can test. Evidence you can trace. Decisions you can explain.
Explore the evidence
Independent work. Explicit assumptions. Inspectable results.
Executive observatory
A working view of the portfolio’s modeled risk register and automated technical checks.
Loading the portfolio register…
Select a cell to inspect its scenarios. Ordinal scores, not predicted financial loss.
Checking evidence availability…
A passing technical test supports only its stated scope. Missing access is “unknown”; old evidence is “stale”.
Historical simulation. Days are calculated from the modeled due dates; current closure evidence has not been supplied.
Ten original project domains, organized around the decisions a security team needs to make.
Control mapping, customer assurance, procurement responses and processor governance.
Domains 1, 4, 8, 9
AI inventory, vendor triage, transparency evidence and local prompt screening.
Domains 2, 3, 6, 7
Scheduled collectors, explicit findings, freshness checks and executive risk reporting.
Domains 5, 10
Change a vendor intake assertion. Inspect how the recommendation changes. This browser demonstration does not call an AI model.
Recommendation
Illustrative triage only. An accountable reviewer must verify the evidence and approve the decision.
The person behind the work
I work at the intersection of technology risk, security assurance and AI governance.
Based in Petaling Jaya, Malaysia, I’m building independent governance systems that make the reasoning visible: what was tested, what the evidence supports and what still needs a decision.
My portfolio covers fifteen control domains, fifteen AI use cases and ten vendor scenarios. These are work samples, with modeled data and explicit limitations.
Inspect my GitHub ↗Professional profile ↗GRC · Technology risk · AI governance