Customer assurance that can be defended
Structure security and compliance responses around approved evidence, accountable owners, review cadence and explicit exceptions so recurring diligence is consistent and inspectable.
Technology Risk & AI Governance
Enterprise Assurance · Third-Party Risk · AI Governance
Kuala Lumpur, Malaysia · governance architecture portfolio
Profiles
Md. Abdullah Al Owasi · Technology Risk & AI Governance
I design the operating logic behind technology risk, control assurance, third-party governance and AI risk: requirements, controls, evidence, ownership, exceptions, remediation, monitoring and residual-risk decisions. The portfolio is built so a reviewer can inspect how the reasoning works, not just read a list of frameworks.
governance systems designed from requirement to decision
AI use cases mapped across risk, oversight and transparency
buyer-diligence questions connected to evidence paths
vendor-risk questions structured for criticality and evidence
Signature operating model
Requirement → control → evidence → exception → residual risk → decision.
Business value
Customer assurance, control operations, technology risk, third-party governance and AI risk all converge on the same problem: turn requirements into evidence-backed decisions that technical and business stakeholders can act on.
Architecture
Customer assurance, third-party risk and AI governance are treated as connected operating problems. Each layer follows the same discipline: requirement → control → evidence → exception → residual risk → decision.
Selected systems
Ten systems spanning assurance, technology risk, third-party risk and AI governance. Each shows the operating logic, evidence path, ownership model, exception state and decision structure behind the work.
Capabilities
Each capability points to a system, artifact, control model or decision structure that can be inspected and discussed in a technical interview.
05 / Operating thesis
My operating thesis is simple: material requirements need accountable controls; controls need evidence; exceptions need treatment; residual risk needs a decision owner. The portfolio applies that logic across assurance, third-party risk and AI governance.
06 / Framework depth
Framework knowledge matters when it changes how controls are designed, evidence is collected, ownership is assigned, exceptions are handled and decisions are made. These are the primary lenses behind the portfolio architecture.
Direct conversation
I am open to high-ownership opportunities across Technology Risk, GRC, Security Compliance, Third-Party Risk and AI Governance. Send the role, business context and hardest unresolved risk question. My portfolio shows the architecture and decision logic I would bring to the conversation.