I am a BS Information Technology student building practical skills in Cloud Security, Security Operations, Governance, Risk & Compliance (GRC), Networking, Linux, and defensive security engineering.

My approach is hands-on: I build, test, document, and improve security-focused systems to understand how security controls work in practice.

My current interests include:

• ☁️ Cloud Security
• 🛡️ Security Operations & Defensive Security
• 📋 Governance, Risk & Compliance (GRC)
• 🌐 Networking & Linux
• 🐍 Python Security Automation
• 🔎 Security Monitoring & Threat Detection
• 🤖 AI-assisted Security Analysis
• 📊 Security Evidence & Risk-oriented Analysis

Cloud Security
├── Identity & Access Management
├── Least Privilege
├── Security Controls
├── Logging & Monitoring
└── Secure Architecture

GRC
├── Risk Management
├── Security Governance
├── Security Controls
├── Compliance Concepts
└── Control Mapping

Security Engineering
├── Security Monitoring
├── Log Analysis
├── Threat Detection
├── Event Correlation
├── Automation
└── Defensive Tooling

• Python
• C++
• Java
• SQL / MySQL
• Pandas
• NumPy

• Cloud Security
• Security Operations (SecOps)
• Security Monitoring
• Log Analysis
• Threat Detection
• Event Correlation
• Networking
• Linux
• Security Automation
• Governance, Risk & Compliance (GRC)

• Streamlit
• Ollama
• Retrieval-Augmented Generation (RAG)
• Evidence-grounded AI workflows
• Local LLM applications
• Tool orchestration
• Security-focused application design
• Session and memory management

KiroTrace is an offline-oriented security monitoring and AI-assisted analysis project built to demonstrate practical SecOps, defensive security engineering, evidence-grounded RAG, controlled security tooling, auditability, and security automation.

                    ┌──────────────────────┐
                    │    Local Log Data    │
                    │      .log / .json    │
                    └──────────┬───────────┘
                               │
                               ▼
                    ┌──────────────────────┐
                    │        Parser        │
                    │ Normalization / Dedup│
                    └──────────┬───────────┘
                               │
                               ▼
                    ┌──────────────────────┐
                    │   Detection Engine   │
                    │    Security Rules    │
                    └──────────┬───────────┘
                               │
                               ▼
                    ┌──────────────────────┐
                    │      Correlator      │
                    │   Event Correlation  │
                    └──────────┬───────────┘
                               │
                               ▼
                    ┌──────────────────────┐
                    │    Incident Engine   │
                    │ Assessment & Context │
                    └──────────┬───────────┘
                               │
                ┌──────────────┴──────────────┐
                ▼                             ▼
       ┌──────────────────┐          ┌──────────────────┐
       │     Local RAG    │          │  Security Tools  │
       │ Evidence Search  │          │ Policy Controlled│
       └────────┬─────────┘          └────────┬─────────┘
                │                             │
                ▼                             ▼
       ┌──────────────────┐          ┌──────────────────┐
       │     Local LLM    │          │    Audit Log     │
       │      Ollama      │          │      JSONL       │
       └────────┬─────────┘          └──────────────────┘
                │
                ▼
       ┌─────────────────────────────────────┐
       │       Streamlit Security UI         │
       │   Evidence-Grounded AI Assistant    │
       └─────────────────────────────────────┘

KiroTrace is designed around:

• Local-first processing
• Evidence before inference
• Controlled tool execution
• Explicit policy enforcement
• Separation of RAG and tool execution
• Security action auditability
• Deterministic fallback behaviour
• Output validation
• Confidence normalization
• Context-aware session memory

Python
Streamlit
Ollama
RAG
Docker
Linux
Git
JSON / JSONL
Local Security Logs

🔗 View KiroTrace

🔗 View Full CyberSecurity Portfolio

Selected project screenshots and implementation evidence are maintained inside the project repository.

For KiroTrace, the evidence includes the project structure, security monitoring interface, analysis workflow, and supporting security functionality.

🔗 View KiroTrace Screenshots & Documentation

My security portfolio contains practical work focused on security monitoring, defensive engineering, networking, automation, and security-oriented application development.

Security Monitoring
        ↓
Log Analysis
        ↓
Threat Detection
        ↓
Event Correlation
        ↓
Incident Analysis
        ↓
Security Automation
        ↓
Evidence-Grounded AI
        ↓
Cloud Security / GRC

🔗 Explore My CyberSecurity Portfolio

• Cloud security architecture
• Identity & Access Management
• Least privilege
• Security controls
• Logging & monitoring
• Secure configuration
• Cloud risk concepts

• Risk identification
• Risk assessment
• Security governance
• Security controls
• Compliance concepts
• Control mapping
• Security documentation

• Security monitoring
• Log analysis
• Detection engineering
• Incident analysis
• Security automation
• Evidence collection
• Defensive tooling

• Computer networking
• Linux
• Containers
• Git & GitHub
• Local development environments

University of Layyah — Pakistan

2024 – 2028

Relevant areas of study include:

• Computer Networks
• Algorithms & Problem Solving
• Programming
• Databases
• Information Technology
• Security-related technologies

Completed coursework covering foundational and practical cybersecurity concepts across a multi-course cybersecurity specialization.

I focus on building projects that demonstrate how security systems actually work, rather than only presenting theoretical concepts.

My workflow:

Understand
    ↓
Design
    ↓
Implement
    ↓
Test
    ↓
Validate
    ↓
Document
    ↓
Improve

For security-focused projects, I pay particular attention to:

• What can go wrong?
• What security control prevents it?
• What evidence demonstrates the control?
• What happens when the control fails?
• Can the behaviour be audited?
• Can the result be reproduced?