Independent security researcher · Ghana

Find and fix website weaknesses before attackers do.

I help Ghanaian businesses and organizations identify web-application vulnerabilities through authorized, controlled security assessments—with clear reports and practical remediation guidance.

01Authorization-firstScope agreed in writing
02Confidential reportingFindings shared privately
03Practical remediationGuidance developers can use
04Ghana-basedAvailable for project inquiries

01 / Services

A clear starting point for a safer website.

Choose a focused review or start with a conversation about your application, priorities, and budget. Scope, targets, credentials, timeline, and deliverables are agreed before testing begins, so pricing is quoted per engagement.

01

Website Security Check

For business websites and portals. Passive checks, exposed-information review, configuration observations, and a concise findings summary.

Discuss this package ↗
03

API Security Review

For products with mobile or public APIs. Endpoint inventory, authorization checks, validation review, and a prioritized report.

Discuss this package ↗
04

Retest & Fix Verification

For teams that have applied fixes. Follow-up checks and a verification note showing which findings were resolved within the agreed scope.

Discuss this package ↗
DELIVERABLE / IN DEVELOPMENT

02 / Your report

Evidence your team can act on.

A redacted sample report is being prepared. The final format is designed to help both decision-makers and developers understand what matters next.

Executive summaryScope & authorizationFinding & severityImpact explanationRedacted evidenceRemediation guidance

The sample will be published here when a suitable redacted example is available. No client identity or confidential finding is shared without permission.

03 / Why organizations choose Gisbounty

Specific, respectful, and useful.

More than 200 security reports have been written across private research and client-facing work. Because reports and client praise are confidential, names, screenshots, and quotes are shared only when the owner gives permission.

Private references and redacted evidence can be discussed when appropriate.

01Permission before probing.

Every active assessment begins with written authorization and a defined scope.

02Controlled validation.

Testing methods and prohibited actions are agreed in advance to minimize disruption.

03Findings with context.

Reports explain business impact, evidence, and prioritized next steps—not just technical labels.

04Support after delivery.

Talk through remediation and arrange retesting when your fixes are deployed.

05Client praise stays private.

Testimonials are available for private review; public quotes wait for written permission.

06Evidence without exposure.

Reports can be redacted for learning and portfolio use without revealing client identities or sensitive findings.

04 / How it works

From first conversation to a stronger website.

  1. 01
    Discuss the website

    Share your application type, goals, concerns, and the systems you want reviewed.

  2. 02
    Confirm authorization & scope

    Agree in writing on permitted targets, methods, timeline, and reporting expectations.

  3. 03
    Assess & validate

    Carry out the agreed checks, validate findings safely, and minimize disruption.

  4. 04
    Deliver & strengthen

    Receive actionable findings, discuss fixes, and request optional retesting.

05 / Selected work

Projects that show how I think.

Alongside research, I build practical web projects focused on digital tools, security education, and accessible learning.

06 / Certificates

Proof of continued learning.

Selected certificates and completed assessments that support my ongoing work in cybersecurity and responsible security research.

06 / About Gisbounty

Research-led security, with real-world curiosity.

I’m an independent security researcher offering authorized website and web-application assessments, responsible-disclosure support, and remediation guidance. I also design and build responsive web projects with secure development fundamentals in mind.

07 / FAQ

Good questions belong in the scope.

Do you test websites without permission?

No. Active testing starts only after the owner or an authorized representative gives written permission and the target scope is agreed.

What information do you need before starting?

Usually the target URLs or app details, your goals, test accounts or credentials where needed, an authorized contact, prohibited actions, and the preferred timeline.

Will testing affect users or production systems?

The approach and prohibited actions are agreed in advance. Testing is controlled and designed to minimize disruption, but no assessment can promise zero operational risk.

Do you access customer data?

The goal is to avoid unnecessary access. If data exposure is relevant to a verified finding, it is handled minimally, documented responsibly, and reported privately.

How long does an assessment take?

Timing depends on the number of targets, application complexity, access provided, and agreed scope. A realistic timeline is discussed before work begins.

What does the final report include?

Scope and authorization, validated findings, severity context, affected features, safely redacted evidence, impact, and practical remediation guidance.

Do you offer retesting?

Yes. Follow-up verification can be scoped after fixes are deployed to confirm whether reported findings were resolved.

Do you accept responsible-disclosure reports?

Yes, when the report concerns a platform that you are authorized to represent. Please use the contact details below and include enough context for a safe, private response.

READY WHEN YOU ARE

Not sure how secure
your website is?

Tell me what your website does and what kind of help you’re looking for. We can start with a scoped conversation.

Assessments are conducted only with the website owner’s permission and an agreed scope. No guarantee of a vulnerability-free website is implied. One phone contact · two email options.