THE FIRST SIGNAL
Discovery.
It starts with something worth a closer look.
A public service, application, endpoint, or infrastructure detail catches my attention. It is a lead to investigate, not an assumption that a vulnerability exists.
BEYOND THE TECHNICAL FINDING
A little about the research, the effort behind each report, and why I believe security matters to everyone.
Hi, and thank you for taking a few minutes to read this.
My reports stay technical, as they should. This page is simply a short note about the person behind the research, what I do, and why I do it. It is not a portfolio or a sales pitch.
A report is the result. There is a person behind the work that led to it.
THE RESEARCHER
Independent security research, driven by curiosity.
I'm an independent security researcher from India. I explore websites, web applications, APIs, and internet-facing infrastructure for weaknesses that could put organizations or their users at risk.
My work includes:
I work independently: no team assigning targets, just me, a laptop, a few tools, and a lot of curiosity. You never really know what you'll find when you start looking.
“Spot something small. Understand how it works. Figure out what could go wrong.
WHY I KEEP RESEARCHING
I do this because I enjoy the process. Not every finding is critical, and not every report leads somewhere. But even a small misconfiguration or unnecessarily exposed service, fixed in time, can help prevent a real incident. When you enjoy something, you keep coming back.
SECURITY IS FOR EVERYONE
Security is not only for software or technology companies. Individuals, small startups, hospitality services, mechanical businesses, accounting firms, and large organizations all use systems, handle information, and depend on services that need protection.
From one person to a growing business to a large organization — security matters to all of us.
FROM OBSERVATION TO DISCLOSURE
A report may look simple when it reaches your inbox. Getting there takes care, verification, and six practical stages.
THE FIRST SIGNAL
A public service, application, endpoint, or infrastructure detail catches my attention. It is a lead to investigate, not an assumption that a vulnerability exists.
ESTABLISHING CONTEXT
I trace domains, subdomains, infrastructure, and public information to identify the asset owner and the right organization or contact. Attribution can take time.
UNDERSTANDING THE ISSUE
Within the relevant scope, I test how the service works and check whether access controls, data, or functionality are exposed. I verify the weakness before reporting it.
MEASURING CONSEQUENCES
I determine what an attacker could realistically do, such as access information or functionality without authorization. I explain the impact clearly, without exaggeration.
MAKING IT ACTIONABLE
I provide clear evidence, reproduction steps, impact, and practical remediation guidance so the team can validate and address the issue without guesswork.
RESPONSIBLE DISCLOSURE
I contact the appropriate team, follow its disclosure process, and stay available for questions. Then comes the wait: a response may arrive quickly, take weeks, or never come.
What reaches your inbox is the end of a process that may have begun with one small observation.
THE HUMAN SIDE
Responsible disclosure involves people on both sides of a report.
Not every report gets a reply. Sometimes I learn that an issue was fixed without hearing back. I understand that teams are busy, and nobody owes me a conversation. Still, a short acknowledgment can mean more than people expect.
Some of the kindest replies have come from small companies managing everything themselves, often without a dedicated security team. They still took the time to say thank you. I appreciate those people more than they know.
“A small acknowledgment can make a meaningful difference to the person behind a report.
THE HUMAN SIDE OF RESPONSIBLE DISCLOSURE
RECOGNITION
I value monetary rewards, and I don't think there's anything wrong with saying so. Independent research takes time, tools, and personal resources, while payment is never guaranteed.
If your organization can offer a bounty or a small token of appreciation, I'd be grateful. If there is no budget or formal program, I completely understand. My main goal is to help you fix the issue. I'm not doing this only for money, but I won't pretend it doesn't matter. Both can be true.
A PERSONAL NOTE
One final thought for the person reading my report.
If you've received a report from me, thank you for taking the time to review it. Behind the technical details is an independent researcher who investigated, documented, and responsibly brought the issue to your attention.
I do this because I enjoy the work and believe it can help. Thank you for taking security seriously and for any action you've taken to address the finding.
IF THERE'S ONE THING I'D LIKE YOU TO TAKE AWAY
A vulnerability report may arrive as an email, a ticket, or a few pages of technical detail.
Behind it is a person who invested time and effort to help make systems safer. A few words of acknowledgment can show that effort mattered.
Stay secure, and take care!
— AN INDEPENDENT SECURITY RESEARCHER