Defend the systems.

Cloud security engineering — useful guardrails, measurable detection, and infrastructure that developers can trust.

Role
Cybersecurity engineer
Focus
Cloud security
Based in
Sri Lanka
Status
Open to relocation

Security that makes momentum possible.

  1. Cloud foundations

    Designing landing zones, identity boundaries, logging, and policy guardrails that scale with the organization.

    • AWS / Azure
    • IAM
    • Policy as code
  2. Detection & response

    Turning cloud telemetry into useful signals, triage playbooks, and response workflows that reduce uncertainty.

    • SIEM
    • Threat detection
    • Incident response
  3. Secure delivery

    Embedding security checks into CI/CD so teams find issues early without slowing down delivery.

    • GitHub Actions
    • IaC scanning
    • Supply chain

Reference projects.

Illustrative projects that show how I approach the work. Real write-ups will replace these as they are published.

  1. Cloud governance · AWSIllustrative

    Guardrails without friction

    A reference landing zone that combines least-privilege access, centralized audit trails, and preventive controls with a clear developer path.

    Discuss this project: Guardrails without friction
  2. Detection engineering · CloudTrailIllustrative

    From noisy logs to signals

    A detection pack for suspicious identity activity, with tested hypotheses, severity context, and response notes for an on-call team.

    Discuss this project: From noisy logs to signals
  3. DevSecOps · GitHub ActionsIllustrative

    Security in the pull request

    A lightweight pipeline for secrets, dependencies, infrastructure, and container checks with actionable developer feedback.

    Discuss this project: Security in the pull request

Credentials.

Hands-on AWS training across cloud foundations, security, and machine learning. Each badge links to its record on Credly.

All badges on Credly

Clear thinking. Practical outcomes.

Good security engineering is not a gate at the end of delivery. It is a set of well-designed decisions that help a team move with confidence.

I work from threat models and real operational constraints, then turn them into controls people can understand, automate, and improve. The goal is a safer system and a stronger engineering culture.

  1. Understand the system

    Map assets, identities, data flows, and the risks that matter to the business.

  2. Reduce the blast radius

    Prefer small, composable controls over brittle security theatre.

  3. Make the secure path easy

    Build feedback loops and defaults that work with the team, not against it.

Let's make your systems safer to move fast in.

[email protected]

Based in Sri Lanka · open to relocation