Bishal Chapagain
Portrait of Bishal Chapagain

Bishal Chapagain

DevSecOps engineer. I secure pipelines and applications across the SSDLC, and focus on cloud security on AWS and software supply chain security. Lately, I'm digging into AI for red teaming.

  • AWS Certified Security – Specialty
  • AWS Certified Solutions Architect – Associate
  • AWS Community Builder
  • Based in Nepal, UTC+05:45

Bishal's assistant

Online

Hi, I'm Bishal's assistant. Ask me anything about his work, skills, certifications or blog, or tap a question below.

Work

  1. – present

    Associate DevSecOps Engineer

    Genese Solution, Lalitpur (hybrid)

    • Secure AWS environments and build security checks into the delivery pipeline.
    • Harden CI/CD pipelines and the software supply chain, with SAST, DAST and SCA scans so issues surface before release.
    • Work on container security, compliance automation, vulnerability management and threat detection.
  2. –

    Cloud Intern

    Genese Solution, Lalitpur

    • Hands-on work with AWS cloud services and Docker, before moving into the DevSecOps role.
  3. Bachelor's degree, Networking and Cyber Security

    University of Computer Science and Skills

Community

Skills

Defense in depth, from the design of an AWS account down to what runs inside a container.

  1. Architecture

    Secure, resilient and cost-aware AWS designs that stay up when load changes.

    • Multi-AZ
    • Auto Scaling
    • Elastic Load Balancing
  2. Identity and data

    Least-privilege access, encryption by default, and logs you can trust.

    • IAM
    • KMS
    • EBS encryption
    • Cognito
    • CloudTrail
    • AWS Config
  3. Delivery pipelines

    Security checks inside CI/CD, so issues surface before release instead of after.

    • SAST
    • DAST
    • SCA
    • Jenkins
    • GitHub Actions
    • Ansible
  4. Supply chain security

    Dependencies, build systems and the pipeline itself treated as attack surface, not trusted by default.

    • SCA
  5. Containers

    Hardened images and runtime settings, tested against the escapes attackers actually use.

    • Docker
    • Rootless mode
    • SELinux
    • AppArmor
    • Kubernetes
  6. Detection and response

    Threat detection and vulnerability management once systems are live.

    • GuardDuty
    • Security Hub
    • Linux

AI red team lab

The newest part of my work, and the part I'm learning in public. I'm exploring how AI systems fail under attack, using open-weight models that run locally, so experiments stay private and nobody else's system is on the receiving end.

Codes are from the OWASP Top 10 for LLM Applications. You can try all ten on the assistant at the top of this page, in the Jailbreak me tab. For why agents break classic threat models, read Your threat model assumes the system holds still.

Blog

Long-form notes on supply chain security, cloud security and AI.

  1. What SLSA actually promises (and what it doesn’t)

    A beginner’s guide to software supply chain security.

  2. Four supply chain attacks that changed how I think about software security

    We started the project last spring. New service, six weeks to ship, so we did what everyone does and reached for the ecosystem. By the time the first build went green the lockfile had 1,247 entries in it. We had chosen…

  3. Your Threat Model Assumes the System Holds Still. Your AI Agent Doesn’t.

    A security practitioner’s guide to STRIDE, DREAD, PASTA, and why agentic AI needs MAESTRO.

All posts

Certifications

Play

Contain the breach. An attacker has a foothold in the middle of the network and is heading for the internet. Each turn you isolate one host, then the attacker moves one hop. Cut off every route out before they get there.

Moves
0
Hops to the internet
5
Your best
–
  • Attacker
  • Attacker's next hop
  • Isolated host
  • Compromised on the way
  • Internet edge

Contact

The fastest way to reach me is a LinkedIn message.

I'm in Nepal, UTC+05:45.

guest@bishal: ~