> initializing_connection...

SECURING THE
DIGITAL FRONTIER

Penetration Tester / Security Analyst / Red Teamer

View Operations Initiate Comms

# whoami

Building practical offensive security workflows focused on discovery, validation, and reporting.

Engineering-first approach to security. I analyze architecture to identify failure modes, validating findings through manual reproduction rather than reliance on automated scanners.

mindset: discovery -> validation -> remediation | ethics > ego

$ status --current
Role : VAPT Intern / Junior Pentester Focus : Web App Security, Logic Flaws, Reporting Location : India | Open to relocation (Bangalore) Availability : Open to Internships / Junior Roles
$ tail -f learning_queue.log
TODO Bug bounty methodology TODO Advanced web exploitation patterns DONE Network pivoting techniques DONE Custom security tooling

# operations_log

🛡️

SentinelMesh

Local-first network visibility ecosystem designed for privacy-conscious environments. Engineered to detect anomalies without external data leakage.

PythonFastAPIReal-time Analysis

status: internal

view_source
🧠

TriBrain

Internal pentest orchestration assistant. Enforces methodology consistency and structures raw findings into reporting-ready evidence.

Workflow AutomationEvidence Management

status: ongoing_internal_tool

view_source_denied
🔬

Web App Security Labs

Structured documentation of manual exploitation techniques. Focus on logic flaws, race conditions, and complex trust boundary violations.

Manual ExploitationLogic Flaws

status: ongoing_research

view_methodology

# capabilities

state: skills_in_active_use

> Red_Team

focus: discovery → validation → reporting

Attack surface mapping Manual vulnerability validation Logic flaw discovery Report-grade reproduction

> Blue_Team

focus: detection → triage → response

Log-based attack detection Incident triage workflows Traffic anomaly analysis

> Builder_Mode

focus: reduce friction, increase signal

Security tooling development Recon/report automation Local-first monitoring systems UX for security engineers
[ how_i_work ]
how_i_work:
  • - collaborate & coordinate tasks
  • - frame problems before solving
  • - document findings clearly
  • - adapt through feedback loops
  • - balance learning with delivery

# experience_log

Sep 2023
Event Coordinator
Techtronix
Jun 2025
Cybersecurity Intern
IIT Madras (Mechanica 2025)
Jul 2025 – Oct 2025
Cybersecurity Virtual Intern
Deloitte (Forage)
Oct 2025 – Jan 2026
Cybersecurity & Ethical Hacking Training
Boston Institute of Analytics (BIA)
(4 Months)
Dec 2025 – Present
VAPT Intern
Gateway Software Solutions

# threat_thinking

When I look at an application, I do not start with tools. I start with questions.

Mental model:

1. What does this system trust by default?
2. Who is allowed to interact with it?
3. Where does user-controlled data enter?
4. What assumptions are being made?
5. What happens if one assumption is wrong?

I focus more on:
• Logic flaws over payloads
• Trust boundaries over endpoints
• Design intent over implementation details

My goal is not to break applications, but to understand how they fail so they can be designed more securely.

# initiate_comms

secure_channel.exe

> establishing secure channel...

> identity: security_engineer

> status: ready

$ connect --contact

email: adriananthony0832@gmail.com

linkedin: https://www.linkedin.com/in/a-adrian0832


status: open to professional conversations

note: student operator | learning mode enabled