Home Services About Clients Collaborate Contact
Security Consulting

Security before
adversaries arrive

Rexscot delivers enterprise-grade penetration testing, VAPT assessments, and application security consulting for organisations that cannot afford to be breached.

Scroll
Web Application Security
API Security Testing
VAPT
Mobile Security
Desktop Application Testing
Secure Code Review
Security Consulting
Threat Modelling
Web Application Security
API Security Testing
VAPT
Mobile Security
Desktop Application Testing
Secure Code Review
Security Consulting
Threat Modelling

Our Discipline

Precise, human-led security testing. Every engagement.

We believe that meaningful security can only come from people who think like attackers. Automation has its place; judgment does not scale.

5+
Applications Tested
16+
Vulnerabilities Found
100%
Satisfaction
I
Human-led, not scanner-driven
Every engagement is conducted by experienced practitioners. We use tooling to accelerate reconnaissance — not to replace the analyst's mind.
II
Reports that drive remediation
Technical depth for developers. Executive clarity for leadership. Every finding includes CVSS scoring, working proof-of-concept, and step-by-step remediation.
III
Confidentiality as a first principle
Mutual NDAs precede every technical conversation. Your architecture, your findings, and your vulnerabilities remain strictly between us.
IV
Accountability through retesting
We do not consider an engagement complete until every finding has been remediated and independently verified. Closure is a shared responsibility.

Capabilities

What we test

Rexscot conducts security assessments across every layer of the modern application stack — from network perimeter to business logic.

  • Web Application Penetration Testing
    01
    OWASP Top 10, business logic, authentication, session management, client-side vulnerabilities
  • API Security Testing
    02
    REST, GraphQL, WebSocket — BOLA, JWT analysis, rate limiting, mass assignment
  • VAPT
    03
    Comprehensive vulnerability assessment and penetration testing — internal, external, web and mobile scope
  • Mobile Application Security
    04
    Android static and dynamic analysis — storage, communication, API layer, reverse engineering
  • Desktop Application Testing
    05
    Windows and Electron applications — local privilege escalation, insecure storage, update mechanism review
  • Security Consulting
    06
    Architecture review, threat modelling, secure code review, risk assessment

Engagement Process

How every
engagement unfolds

A structured, seven-phase process that ensures nothing is missed from initial reconnaissance through to verified remediation.

Phase 01
Reconnaissance
Passive and active information gathering across all declared scope.
Phase 02
Attack Surface Mapping
Enumeration of entry points, endpoints, and potential attack vectors.
Phase 03
Vulnerability Discovery
Systematic discovery using manual testing augmented by targeted tooling.
Phase 04
Exploitation & Validation
Manual exploitation of confirmed vulnerabilities with working proof-of-concept.
Phase 05
Risk Assessment
CVSS-based scoring contextualised against real business impact.
Phase 06
Report Delivery
Executive summary and full technical report with remediation guidance.
Phase 07
Remediation & Retest
Available for developer queries. Independent verification once fixes are applied.

Why Rexscot

Principles that shape
every engagement

01
Human Expertise
Every assessment is conducted by practitioners, not configured in a dashboard. Human judgment finds what automated scans miss.
02
AI-Assisted Reconnaissance
Agentic AI workflows surface attack surfaces faster and more thoroughly — giving our analysts more time for deep manual analysis.
03
Actionable Reporting
Reports written for two audiences simultaneously — technical teams who need to fix, and leadership who need to decide.
04
NDA-First Engagement
A mutual NDA is standard practice, signed before any discussion of your systems, architecture, or infrastructure begins.
05
Verified Remediation
We retest after fixes are applied. We do not consider an engagement closed until every confirmed vulnerability is independently verified as resolved.
06
Responsive Communication
Status updates throughout the engagement. Developer queries answered during remediation. No period of silence once work has begun.

Report Quality

Deliverables that
drive action

Every report includes an executive summary for leadership, a complete technical report for engineering teams, CVSS-scored findings, working proof-of-concept code, and step-by-step remediation guidance.

CriticalSQL Injection — /api/users authentication bypass
HighBroken Object Level Authorisation (IDOR)
HighJWT Algorithm Confusion — RS256 to HS256
MediumReflected XSS via unsanitised search parameter
MediumInsecure Direct Object Reference on document API
rexscot-pentest-report.txt
# Rexscot — Engagement Report
# Client: [REDACTED] | Classification: CONFIDENTIAL
 
engagement_type: Web Application VAPT
scope: app.client.com + /api/*
duration: 5 business days
methodology: OWASP Testing Guide v4.2
 
findings_summary:
  critical: 2
  high: 4
  medium: 7
  low: 5
 
overall_risk: CRITICAL (CVSS 9.1)
retest_status: Pending remediation
 
# Executive summary: included
# Proof of concept: included
# Remediation guide: included
# NDA: active

Client Feedback

What our clients say

All client reviews
"Professional engagement throughout. The reporting was detailed, the communication was clear, and every finding was explained with enough context for our engineering team to act on it immediately."
Wistaar
Technology Platform
Web Application VAPT
"The team found critical vulnerabilities in our trading API that had gone undetected. Remediation guidance was practical and the retest confirmed everything was properly resolved."
OpenTradex
Financial Technology Platform
API Security Assessment

Onboarding

From first contact to
secured system

A structured onboarding process that removes ambiguity from the very first conversation.

  • 01
    Initial Contact
    Submit your enquiry. We respond within one business day to discuss your requirements at a high level.
  • 02
    NDA and Agreement
    A mutual non-disclosure agreement is executed before any technical discussion or system details are shared.
  • 03
    Scope Definition
    Together we define the exact scope, timeline, rules of engagement, and testing methodology for the assessment.
  • 04
    Security Testing
    The engagement runs to the agreed schedule. Regular status updates are provided throughout the testing period.
  • 05
    Report Delivery
    Technical and executive reports delivered securely, accompanied by a debrief call to walk through findings.
  • 06
    Remediation Support
    Our team remains available to answer developer questions as your engineers apply the recommended fixes.
  • 07
    Retest and Sign-off
    Once fixes are applied, we independently verify each remediation. A retest report is issued upon completion.

Standards and Ethics

Security conducted
responsibly

01
OWASP Methodology
All web assessments are conducted in accordance with the OWASP Testing Guide v4.2.
02
Responsible Disclosure
Findings are reported through coordinated disclosure with clear timelines and no unilateral publication.
03
NDA by Default
Mutual NDA is executed at the beginning of every engagement, before any technical discussion.
04
Risk-Based Prioritisation
Findings are triaged by real business impact, not raw CVSS scores in isolation.
05
Data Handling
All client data is encrypted in transit and at rest, then deleted per the terms agreed at engagement start.
06
Verified Remediation
No engagement is formally closed until retesting confirms all critical and high findings are resolved.

Pricing

Every assessment is scoped individually

Custom Quotation
No two assessments share the same scope, complexity, or timeline. We price each engagement based on what your business actually requires — no fixed packages, no unnecessary overhead.
Scope and asset count Application complexity Testing depth Timeline requirements Retest cycles
Request a Quotation

Common Questions

Frequently asked

A penetration test is an authorised, simulated attack against your systems designed to identify and safely exploit vulnerabilities before real adversaries do. Unlike automated scanning, a pentest involves human expertise and lateral thinking to uncover complex, business-logic flaws that tools cannot detect.
VAPT — Vulnerability Assessment and Penetration Testing — combines a systematic audit for known vulnerabilities with manual exploitation and validation. It provides both breadth (what exists) and depth (what can be exploited) of security coverage in a single structured engagement.
Duration depends on scope and complexity. A focused web application assessment typically requires three to seven business days. Comprehensive VAPT engagements or multi-application assessments may require two to four weeks. We agree on timelines during the scope definition phase.
Yes. Following report delivery, we remain available to answer developer questions and provide clarification as your engineering team applies the recommended fixes. Retesting is then conducted to independently confirm each vulnerability is resolved.
Yes. We work with startups, growth-stage companies, SMEs, and enterprises. For earlier-stage organisations, we offer focused, scope-controlled assessments that deliver maximum value relative to the investment.
A mutual NDA is standard practice at Rexscot, executed before any technical discussion or sharing of system details. This is not optional — it is how every engagement begins.
Yes. Retesting is included in every engagement. Once your team applies the recommended fixes, we verify each remediation independently and issue a retest report confirming the outcome.

Begin

Identify your vulnerabilities
before attackers do

No commitment required for an initial consultation. Tell us about your business and we will recommend the right assessment.

Capabilities

Security testing across every layer of the modern stack

From perimeter to business logic, Rexscot conducts manual assessments across web, API, mobile, and desktop applications.

01 — Web Application

Web Application
Penetration Testing

Deep-dive manual testing against the OWASP Testing Guide — uncovering vulnerabilities that automated scanners cannot detect, including business logic and authentication flaws.

  • —
    OWASP Top 10 — full coverage
    All ten categories tested systematically using manual techniques.
  • —
    Business Logic Testing
    Abuse of application workflows, pricing manipulation, and privilege abuse scenarios.
  • —
    Authentication and Session Security
    Login bypass, session fixation, token predictability, and MFA circumvention.
  • —
    Injection and Client-Side Vulnerabilities
    SQLi, XSS, CSRF, SSRF, XXE, and file upload abuse testing.
coverage-matrix.txt
# Web Application Test Coverage
 
A01: Broken Access Control [COVERED]
A02: Cryptographic Failures [COVERED]
A03: Injection [COVERED]
A04: Insecure Design [COVERED]
A05: Security Misconfiguration [COVERED]
A06: Vulnerable Components [COVERED]
A07: Auth Failures [COVERED]
A08: Software & Data Integrity [COVERED]
A09: Security Logging [COVERED]
A10: Server-Side Request Forgery [COVERED]
 
business_logic: COVERED
manual_testing: YES
poc_included: YES

02 — API Security

API Security Testing

Category
Authorisation
BOLA, BFLA, IDOR, scope bypass, horizontal and vertical privilege escalation across all endpoints.
Category
Authentication
JWT algorithm confusion, weak secrets, OAuth misconfigurations, token expiry and refresh issues.
Category
Data Exposure
Excessive data in responses, error leakage, sensitive field exposure, mass assignment vulnerabilities.
Category
Rate and Logic
Rate limiting bypass, GraphQL introspection abuse, injection via query parameters, and batching attacks.

03 — Mobile Security

Mobile Application
Security Testing

Android application assessments covering static analysis, dynamic testing, and backend API communication review.

Android
  • APK decompilation and static analysis
  • Insecure data storage — SQLite, SharedPreferences, external storage
  • Insecure communication and SSL pinning bypass
  • Dynamic instrumentation via Frida
  • Reverse engineering and binary analysis
Backend API Layer
  • Full API security review conducted alongside the mobile assessment
  • Authentication and session handling analysis
  • Access control across all mobile-facing endpoints
  • Token and key management review
  • Sensitive data exposure in API responses

04 — Desktop

Desktop Application Testing

Windows and Electron application assessments — local privilege escalation, insecure credential storage, DLL hijacking, and update mechanism review.

  • Windows application security review
  • Electron — Node.js context isolation and IPC review
  • Local privilege escalation pathways
  • Insecure credential and key storage
  • Update mechanism integrity verification

05 — VAPT

Vulnerability Assessment and Penetration Testing

Comprehensive VAPT engagements covering your full attack surface — internal networks, external perimeter, web applications, and mobile — in a single structured programme.

External
Internet-facing assets and perimeter
Internal
Network infrastructure and systems
Web
Application layer assessment
Mobile
Android and API layer

Get Started

Not sure which assessment you need?

Tell us about your organisation and we will recommend the right engagement.

About Rexscot

Making enterprise-grade security accessible to every serious business

Rexscot was founded with the conviction that thorough, human-led security testing should not be limited to organisations with eight-figure security budgets.

Our Story

We witnessed too many growing businesses treat security as a compliance checkbox rather than an operational requirement. Not because they were careless, but because serious testing felt inaccessible.

Rexscot was built to close that gap. We bring the same depth of security assessment that large enterprises receive to startups and scale-ups who carry equivalent exposure — often with less internal capacity to detect or respond to a breach.

Every engagement is conducted by practitioners who approach your systems the way an adversary would. Findings are communicated clearly enough for engineers to act on them and for leadership to understand what was at stake.

The Team

KS
Kaif Shaikh
Founder & Principal Security Consultant
// Magician Slime
Application security specialist and offensive security researcher. Leads web application assessments, API security engagements, and the development of AI-assisted security workflows used in Rexscot's reconnaissance process.
Web Security API Pentesting AI-Assisted Recon Bug Hunting OWASP
MK
Musaddik Khan
Co-Founder and Security Researcher
// MK
Security researcher and penetration tester with broad expertise across network security, mobile application testing, and vulnerability research across diverse technology stacks. Leads VAPT engagements and infrastructure assessments.
Security Research Mobile Security VAPT Network Security Vulnerability Research

Mission and Vision

Mission

To proactively secure organisations through rigorous offensive security testing and actionable remediation guidance — converting discovered vulnerabilities into strengthened defences.

Vision

A digital ecosystem in which businesses of every scale can build and operate with confidence, knowing their security posture is continuously tested and genuinely resilient.

Core Values

What we stand for

01
Integrity
Transparency without exception. No inflated findings, no undisclosed scope changes.
02
Confidentiality
Your vulnerabilities, your architecture, your data — protected at every stage of every engagement.
03
Transparency
Clear, honest reporting. We explain what we found, what it means, and what to do about it.
04
Technical Excellence
Depth over breadth. Every finding is manually verified before inclusion in any report.
05
Continuous Development
The threat landscape does not stand still. Neither do we.

Ready to begin?

Contact us to discuss your requirements. No commitment for the initial consultation.

Client Reviews

Trusted by organisations that treat security seriously

Verified outcomes from completed engagements.

Web Application VAPT
Wistaar
Technology Platform
Findings
14
Vulnerabilities identified across authentication, session handling, and API layers.
"Professional engagement throughout. The reporting was detailed, the communication was clear, and every finding was explained with enough context for our engineering team to act immediately."
Wistaar
API Security Assessment
OpenTradex
Financial Technology Platform
Critical Findings
1
Critical authorisation bypass in the trading API. All findings remediated and verified.
"The team found critical vulnerabilities in our trading API that had gone undetected. Remediation guidance was practical and specific. Retesting confirmed everything was properly resolved."
OpenTradex

Collaboration

We are open to working with people who take security seriously

Researchers, developers, startups, and organisations building in the security space — we are open to meaningful collaboration.

Who We Work With

01
Security Researchers
Vulnerability research, responsible disclosure coordination, and participation in structured security programmes.
02
Bug Hunters
Partnerships on bug bounty platforms and coordinated disclosure initiatives for shared client programmes.
03
Security Developers
Collaboration on security tooling, automation frameworks, and AI-assisted reconnaissance infrastructure.
04
Organisations
Security partnerships, joint assessments, and co-delivered programmes for enterprise and mid-market clients.
05
Startup Founders
Security-by-design integration for early-stage and growth-stage companies building their security posture from the ground up.
06
Students
Knowledge sharing, mentoring, and educational collaboration for those pursuing a serious path in cybersecurity.

Send an Enquiry

Tell us about your idea

Fill in the form and we will respond within one business day to discuss whether there is a productive fit.

Contact

Discuss your security requirements

Complete the form and we will respond within one business day. All enquiries are treated as confidential.

Email
Business Enquiries
Response Time
Within one business day
Location
India — Remote engagements worldwide
Confidentiality
All enquiries are treated as confidential. A mutual NDA is executed before any technical discussion begins.

Classification: Public

Vulnerability Disclosure Policy

Rexscot welcomes responsible security research. This policy defines how to report vulnerabilities affecting Rexscot's own systems and what researchers can expect from us.

Version
1.0
Status
Draft — Pending Legal Review
Classification
Public
Security Contact
Found a security issue?

Send a detailed report to our security contact. We take every responsible disclosure seriously.

Report a Vulnerability Critical Report

01

Purpose

Rexscot is a cybersecurity consulting firm that provides penetration testing, vulnerability assessment, and security consulting services to organisations across India and internationally. We take the security of our own systems and public-facing assets seriously.

This Vulnerability Disclosure Policy (VDP) establishes a clear and transparent process for security researchers, users, customers, and members of the broader security community to responsibly report suspected vulnerabilities affecting Rexscot's own published in-scope assets.

Rexscot believes in the value of responsible security research and recognises that external researchers may sometimes identify potential security issues before internal teams.

This policy applies exclusively to Rexscot's own published in-scope assets. It does not cover client systems, client infrastructure, or third-party services. Separate engagement documentation governs all client security testing.

02

Scope

2A — In-Scope Assets

The following Rexscot-operated assets are within the scope of this policy. Researchers should verify current scope before conducting any testing.

Asset TypeAsset / IdentifierNotes
Primary Websitehttps://rexscot.comPublic-facing site

Scope may be updated periodically. Always verify current in-scope assets before testing. If uncertain, contact all@rexscot.com before conducting any testing.

2B — Out-of-Scope Assets

  • Infrastructure not listed as in-scope above
  • Third-party services, SaaS providers, and cloud platforms used by Rexscot
  • Internet infrastructure not operated by Rexscot
  • Systems belonging to Rexscot's clients or customers
  • Employee personal accounts and personal devices
  • Physical premises and physical security
  • Social engineering targets including employees, contractors, or partners

2C — Third-Party Systems

Rexscot relies on various third-party providers. These systems are not within scope. Researchers who identify a vulnerability in a third-party system that affects Rexscot may report it to the relevant vendor directly and notify Rexscot separately at all@rexscot.com.

2D — Client and Customer Systems

Important: Rexscot provides security testing services to client organisations. A researcher must not assume that any client domain, application, server, IP address, API, or cloud account is authorised for testing merely because Rexscot works with that organisation. Client systems require separate, written authorisation. Testing client systems without authorisation may constitute a criminal offence.

03

Reporting Channel

ChannelDetails
Security Emailall@rexscot.com
Websitehttps://rexscot.com
Critical ReportsUse subject line: [CRITICAL SECURITY REPORT]

Rexscot recommends researchers use encrypted communication where possible.

04

What to Include in a Vulnerability Report

A complete, well-structured report enables Rexscot to validate and remediate findings efficiently.

FieldRequiredDescription
Researcher Name / AliasOptionalMay be withheld for anonymity
Contact EmailRequiredFor follow-up and status updates
Affected AssetRequiredDomain, URL, application, or service identifier
Vulnerability TypeRequirede.g. SQL Injection, XSS, IDOR, Auth Bypass
DescriptionRequiredClear explanation of the vulnerability and its behaviour
PreconditionsRecommendedAuthentication state, required permissions, etc.
Reproduction StepsRequiredExact step-by-step instructions to reproduce the issue
Proof of ConceptRecommendedCode, payload, screenshot, or HTTP request/response
Affected Endpoints / URLsRequiredExact URLs, API endpoints, or parameters affected
Business ImpactRecommendedWhat could an attacker achieve by exploiting this?
Timestamp / TimezoneRecommendedWhen the issue was discovered and tested
Test Accounts UsedIf applicableAny test accounts used — do not submit passwords

Minimise sensitive data in reports. Do not submit production credentials, private keys, API secrets, or third-party personal data.

05

Safe Reporting Practices

Researchers are expected to conduct vulnerability discovery responsibly and minimise potential harm to Rexscot systems, data, and users.

  • Minimise access to data beyond what is strictly necessary to confirm the vulnerability
  • Avoid accessing, modifying, deleting, or exfiltrating user data or production data
  • Stop testing immediately once sufficient evidence has been gathered
  • Avoid disrupting services, creating outages, or degrading system performance
  • Avoid creating or deploying persistence mechanisms, backdoors, or malware
  • Protect any sensitive information unintentionally accessed during research
  • Promptly notify Rexscot if sensitive or personal information was unexpectedly encountered
  • Securely delete any sensitive data collected once it is no longer needed for the report

06

Permitted Security Research

Within the published scope defined in Section 2A, the following types of low-impact research activities may be acceptable:

  • Passive reconnaissance of publicly accessible information
  • Identification of publicly visible security misconfigurations
  • Low-impact vulnerability verification using controlled proof-of-concept
  • Authentication and authorisation testing strictly within published scope
  • Non-destructive validation of reported issues
  • Automated scanning of limited scope with minimal traffic

Submitting a vulnerability report does NOT authorise broader security testing. Research not covered by published scope requires separate written authorisation from Rexscot.

07

Prohibited Activities

The following activities are explicitly prohibited under this policy regardless of intent:

Service Disruption
DoS, DDoS, load testing, stress testing, or any disruption of services
Data Manipulation
Modifying, deleting, corrupting, encrypting, or exfiltrating production data
Malware & Persistence
Deploying malware, ransomware, backdoors, webshells, or persistence mechanisms
Social Engineering
Phishing, vishing, or pretexting against employees, partners, or clients
Physical Attacks
Physical intrusion or attacks against Rexscot premises
Credential Abuse
Password spraying, brute-force attacks, or credential stuffing
Out-of-Scope Systems
Testing any system, domain, IP, or service not listed as in-scope
Client Systems
Any testing of Rexscot client or customer systems without separate written authorisation
Third-Party Infrastructure
Exploiting third-party provider vulnerabilities via Rexscot
Unsafe PoC
Proof-of-concept exploits creating unacceptable operational, legal, or privacy risk
Unnecessary Exfiltration
Exfiltrating data beyond what is needed to confirm and document a vulnerability

08

Test Data and Account Safety

  • Use researcher-owned or designated test accounts — do not use real user accounts without explicit permission
  • Do not submit real production credentials, passwords, API keys, or private keys in reports
  • Do not retain or publish authentication tokens or session cookies discovered during research
  • Avoid collecting personal information about Rexscot employees, clients, or users
  • Do not access client data beyond what is necessary to confirm the vulnerability
  • If real credentials are inadvertently discovered, notify Rexscot immediately and do not use or retain them

09

Third-Party Services

Rexscot uses third-party services as part of its operations. Third-party infrastructure is not automatically within scope.

Researchers who identify a vulnerability involving a third-party provider should report directly to the relevant vendor's own disclosure programme and may notify Rexscot separately where the issue has direct implications for Rexscot's security posture. Do not exploit or pivot through third-party vulnerabilities to attack Rexscot or its clients.

10

Client and Customer Systems

This section is critical. Rexscot provides penetration testing and security consulting to client organisations. As a result, Rexscot may be associated with a wide range of client domains, applications, and infrastructure.

A vulnerability researcher must not assume that any of the following are authorised for testing under this policy:

  • Client or customer domains and applications
  • Client or customer servers, IP ranges, or cloud accounts
  • APIs or infrastructure that Rexscot manages on behalf of a client

Any security testing of client systems requires a separate, written Authorisation to Test signed by the relevant client, together with a formal Rexscot engagement agreement. Submitting a contact form or vulnerability report to Rexscot does not constitute client authorisation.

Unauthorised testing of client systems may constitute a criminal offence under applicable Indian and international law.

11

Report Handling Process

01
Receipt
Report received at all@rexscot.com. Acknowledgement where practical.
02
Initial Review
Assessment of completeness, scope, and severity.
03
Scope Verification
Confirmation that reported asset falls within published scope.
04
Technical Validation
Internal technical assessment to confirm and reproduce the vulnerability.
05
Risk Assessment
Evaluation of severity and potential business impact.
06
Remediation
Internal coordination and deployment of fixes or mitigations.
07
Researcher Update
Where appropriate, Rexscot may communicate the outcome to the reporting researcher.
08
Closure
Formal closure following verification of remediation.

Rexscot does not commit to fixed response or remediation timelines. Response times may vary depending on report volume, severity, and operational capacity.

12

Communication with Researchers

Rexscot may communicate with researchers at various stages:

  • Acknowledgement of receipt where practical
  • Requests for additional information or clarification
  • Notification of validation outcome (confirmed, out-of-scope, duplicate, or not reproducible)
  • Notification of remediation where appropriate
  • Closure of the report

Rexscot does not guarantee a response to every report. Duplicate, out-of-scope, and invalid reports may not receive an individual response. All communications should be directed to all@rexscot.com.

13

Critical Vulnerabilities

Reports involving any of the following should be clearly marked as [CRITICAL SECURITY REPORT] in the subject line:

  • Active exploitation or evidence of ongoing attack
  • Remote code execution or arbitrary command execution
  • Authentication bypass or complete access control failure
  • Significant unauthorised access to sensitive or personal data
  • Major production system impact or instability
  • Vulnerabilities with direct financial implications
Critical reports

Send to all@rexscot.com with subject: [CRITICAL SECURITY REPORT]

Send Critical Report

14

Responsible Disclosure

Rexscot requests that researchers allow reasonable time to investigate, validate, and remediate reported vulnerabilities before any public disclosure.

Researchers are encouraged to coordinate disclosure timing with Rexscot. Premature public disclosure of an unpatched vulnerability may harm Rexscot's clients, users, and security posture.

Where coordinated disclosure is agreed, Rexscot may consider acknowledging the researcher's contribution, subject to operational and legal considerations. Rexscot does not guarantee public credit, CVE assignment, hall-of-fame listing, or blog recognition.

Rexscot does not impose a mandatory embargo period. Researchers are asked to act in good faith and contact all@rexscot.com to discuss disclosure timing.

15

Public Disclosure

Following remediation, Rexscot may consider coordinated public disclosure where appropriate and where the researcher has acted in accordance with this policy.

Rexscot does not promise: public credit or attribution, CVE ID assignment, hall-of-fame listings, blog posts about specific reports, or monetary compensation of any kind.

This policy is not a bug-bounty programme. No financial rewards are offered or implied.

16

Duplicate and Out-of-Scope Reports

Duplicates

Multiple researchers may independently identify the same underlying vulnerability. Rexscot may classify subsequent reports as duplicates and will acknowledge them where practical.

Out-of-Scope / Invalid

Reports may be classified as out-of-scope or invalid where they involve assets not in published scope, third-party or client systems, theoretical issues without reproducible evidence, automated scanner output without manual validation, or informational observations without security impact.

17

Safe Harbor

Rexscot does not intend to pursue legal action against researchers who:

  • Conduct research within published in-scope assets (Section 2A)
  • Comply with all restrictions in this policy, particularly Section 7 (Prohibited Activities)
  • Report vulnerabilities promptly and in good faith through the designated reporting channel
  • Minimise harm in accordance with Section 5 (Safe Reporting Practices)
  • Do not exploit vulnerabilities beyond confirming the finding
  • Do not publicly disclose before Rexscot has had reasonable time to investigate

This section does not: authorise testing outside published scope, override applicable law, waive the legal rights of third parties including Rexscot's clients, create a contractual relationship, or constitute a legal defence against criminal or civil proceedings.

18

Data Confidentiality

Researchers who submit reports are expected to:

  • Minimise access to sensitive data beyond confirming the vulnerability
  • Not publish, share, or distribute any confidential information encountered during research
  • Securely delete any sensitive data collected as soon as it is no longer needed for the report
  • Notify Rexscot if sensitive personal data, client data, or credentials were unintentionally accessed

Rexscot will treat vulnerability reports submitted in good faith with appropriate confidentiality. Rexscot does not guarantee absolute confidentiality in all circumstances, including where legal or regulatory obligations may require disclosure.

19

AI-Assisted Reporting and Research

Rexscot acknowledges that researchers may use AI-assisted tools and workflows. The following principles apply:

  • AI-generated reports may be submitted; the researcher takes full responsibility for accuracy and completeness
  • Unsupported AI-generated claims without reproducible evidence may require additional supporting information
  • Researchers must not submit Rexscot's confidential information to public AI systems to generate a report
  • Fabricated or misleading AI-generated evidence is not acceptable and may result in the report being dismissed
  • Researchers remain personally responsible for the accuracy, legality, and ethics of their research regardless of AI tool usage

20

Report Quality

High-quality reports enable faster triage and remediation. A useful report includes:

  • A clear, descriptive title summarising the issue
  • Exact, reproducible steps to recreate the vulnerability
  • The specific assets, endpoints, or parameters affected
  • Evidence of exploitability — a working proof of concept, HTTP request/response, or screenshot
  • A concise description of the potential business or security impact
  • The conditions required for exploitation (authentication state, permissions, etc.)
  • Any relevant technical context such as server headers or error messages

Reports that are vague, non-reproducible, or rely solely on automated scanner output without manual validation may be deprioritised or classified as informational.

21

Policy Limitations

This Vulnerability Disclosure Policy:

  • Is not a Master Services Agreement, Statement of Work, or Rules of Engagement
  • Does not create a client engagement or contractual relationship by virtue of submitting a report
  • Does not constitute an authorisation to conduct security testing beyond published scope
  • Does not guarantee remediation of any reported issue
  • Does not offer or imply financial compensation or bug-bounty rewards
  • Does not override applicable law or regulation

All formal security testing engagements require a separate Master Services Agreement, Statement of Work, and signed Rules of Engagement / Authorisation to Test document.

22

Policy Changes

Rexscot may update this Vulnerability Disclosure Policy from time to time. The current version is published at https://rexscot.com/security and /.well-known/security.txt.

Changes are effective from the date indicated in the document control table. Researchers are encouraged to review the current version before submitting reports.

23

Contact

DetailInformation
OrganisationRexscot — Cybersecurity Consulting
Security Contactall@rexscot.com
Websitehttps://rexscot.com
Ready to submit a report?

Include the affected asset, vulnerability type, reproduction steps, and proof of concept.

24

Document Control

VersionDateChangeOwnerStatus
1.02025Initial draftRexscotDraft

Classification: Public

Privacy Policy

This policy explains what information Rexscot collects through this website, how it is used, and how to contact us about privacy matters.

Version
1.0
Status
Draft — Pending Legal Review
Classification
Public
Privacy Contact

01

Introduction

This Privacy Policy explains how Rexscot ("Rexscot", "we", "us") collects, uses, and protects information in connection with the website at rexscot.com ("the Website").

Rexscot is a cybersecurity consulting firm providing penetration testing, vulnerability assessment, and security consulting services.

For questions about this policy or how your information is handled, contact us at all@rexscot.com.

02

Scope of This Privacy Policy

This policy applies to:

  • Visitors browsing the Website
  • People submitting the Contact form or Collaborate form
  • Security researchers submitting vulnerability reports under the Vulnerability Disclosure Policy
  • Prospective clients requesting information about our services

This Website Privacy Policy does not replace contractual confidentiality or data-processing terms contained in a Non-Disclosure Agreement, Master Services Agreement, Statement of Work, Rules of Engagement, or other signed engagement documentation. Where a client relationship is governed by such documents, those documents may contain additional or more specific terms.

03

Information We Collect

A — Information You Provide Directly

When you submit a form on this Website, we receive the information you enter into that form.

FormFields Collected
Contact FormName, company, email address, website/application URL, service required, budget range, preferred contact method, project description
Collaborate FormName, email address, collaboration type, proposal description

Both forms are processed via Netlify Forms (see Section 10). We do not ask for passwords, payment details, or government ID numbers through these forms, and you should not submit them.

B — Information Collected Automatically

The Website itself does not run first-party analytics or tracking scripts, and does not set cookies or use browser local/session storage to identify or track visitors.

Standard web server and hosting-infrastructure logs (for example, IP address, request timestamp, and browser user-agent string) may be generated by our hosting provider as part of normal web server operation and basic security monitoring. These are infrastructure-level logs rather than data actively collected by the Website's own code.

C — Information Received from Third Parties

We do not currently receive personal information about you from third-party data brokers or marketing partners. Form submissions are relayed to us by our form-processing provider (Netlify) as described in Section 10.

D — Information Generated During Communications or Security Reporting

If you email us directly, or submit a vulnerability report, the content of that communication — including any technical details, attachments, or personal information you choose to include — is received and retained as described in Sections 5 and 12.

04

Contact and Communication Information

When you submit the Contact form, request a service, request collaboration, or email us directly, we use the information provided to respond to you and evaluate your enquiry. This is distinct from a security vulnerability report — see Section 5.

Email sent to all@rexscot.com is received directly by Rexscot; the content and any attachments you send are retained as part of normal business correspondence.

05

Vulnerability Reports

Security researchers may submit vulnerability reports under our Vulnerability Disclosure Policy. Vulnerability reports may contain technical information (such as affected endpoints, request/response data, or proof-of-concept code) and, depending on what the researcher chooses to submit, personal information.

Researchers should not submit passwords, private keys, API secrets, unnecessary personal data, unnecessary production data, or confidential third-party information as part of a report.

This Privacy Policy does not weaken or replace the reporting process, scope restrictions, or safe-harbor language set out in the Vulnerability Disclosure Policy at rexscot.com/security.

06

How We Use Information

We use the information described in Section 3 for the following specific purposes:

  • Responding to enquiries submitted through the Contact or Collaborate forms, or by direct email
  • Evaluating and scoping requested security assessment services
  • Communicating with prospective and existing clients about engagements
  • Receiving, triaging, and responding to vulnerability disclosure reports
  • Maintaining the security and integrity of the Website
  • Preventing spam and abuse of Website forms (see Section 10, honeypot field)
  • Maintaining business records of correspondence
  • Meeting legal or regulatory obligations where applicable

We do not use the information collected through this Website for advertising, profiling, or automated decision-making, and we do not sell it — see Section 11.

08

Cookies and Similar Technologies

This Website does not set first-party cookies, and its own code does not use browser local storage or session storage to track or identify visitors.

Netlify, which hosts this Website and processes form submissions, may set a functional cookie or token as part of its Netlify Forms anti-spam and submission-handling mechanism when a form is submitted. This is limited to form-processing functionality rather than tracking or advertising.

Because the Website does not use analytics, advertising, or tracking cookies, no cookie-consent banner is currently presented. This will be reviewed if the Website's technology changes.

09

Analytics

This Website does not currently run any analytics platform (such as Google Analytics or similar). No visitor-behaviour tracking script is loaded by the Website. If this changes in the future, this Privacy Policy will be updated to name the provider, the information it processes, and any controls available to visitors.

10

Third-Party Services and Providers

The Website relies on the following third-party services to operate:

ProviderPurposeInformation Involved
NetlifyWebsite hosting and form submission processing (Contact and Collaborate forms)Form field data you submit; standard hosting request logs
Google FontsWeb font delivery (Playfair Display, DM Sans)Standard font-request connection data (IP address, browser type) per Google's practices
cdnjs (Cloudflare)Delivery of Three.js and GSAP JavaScript libraries used for visual effectsStandard script-request connection data
HostingerDomain name registration for rexscot.comDomain registration data (not visitor data)

These providers process information according to their own privacy policies. Rexscot does not control, and is not responsible for, the internal data practices of these third parties. We selected them for their function (hosting, fonts, script delivery) rather than for any data-collection capability.

11

Data Sharing and Disclosure

We do not sell personal information collected through this Website, and we do not share it with third parties for their own marketing purposes.

Information may be shared in the following limited circumstances:

  • With service providers who process data on our behalf strictly to operate the Website (see Section 10 — Netlify, in particular, for form processing)
  • With professional advisers (such as legal or accounting) where necessary and subject to confidentiality
  • With authorities or regulators where required by applicable law
  • In connection with a legal process, dispute, or the protection of Rexscot's rights or the rights of others

12

Data Retention

We retain information collected through this Website only for as long as reasonably necessary for the purposes described in Section 6, including:

  • As long as necessary to respond to and resolve an enquiry, engagement discussion, or vulnerability report
  • As required to maintain business records and correspondence
  • As required by applicable contractual obligations once a client engagement begins
  • As required by applicable law

13

Data Security

As a cybersecurity consulting firm, we take reasonable, appropriate measures to protect information submitted through this Website, consistent with the confidentiality and evidence-handling principles applied in our client engagements. These measures may include:

  • Restricted access to information received through Website forms and email
  • Secure transmission of form submissions (HTTPS)
  • Data minimisation — collecting only what is needed to respond to a request
  • Careful handling of vulnerability reports in line with our Vulnerability Disclosure Policy
  • Controlled retention of correspondence and reports

No method of transmission or storage is completely secure. We do not claim that any system is "100% secure," and we do not hold any specific security certification (such as ISO 27001 or SOC 2) for this Website unless separately confirmed and documented.

14

Security Incidents

Rexscot takes reasonable steps to protect information handled through this Website. In the event of a security incident affecting personal information, we will respond in accordance with applicable law and our internal procedures.

15

Your Rights

Depending on the law applicable to the processing of your information, you may have rights such as requesting access to, correction of, or deletion of information you have provided to us.

To make a request regarding your information, contact us at all@rexscot.com.

16

Children and Minors

This Website is a business-to-business and professional services website and is not directed at, or designed for, children. We do not knowingly collect personal information from children through this Website.

17

International Data Transfers

Rexscot operates from India. Some third-party service providers described in Section 10 (such as Netlify and Google Fonts) may process or route data through infrastructure located outside India as part of their global service delivery.

We rely on these providers' own security and privacy practices for such processing. We do not have confirmed details of every specific data-routing location for every provider, and this section will be updated with more specific information as it is confirmed.

18

Business and Client Engagement Data

Information processed during a formal client engagement — including scope details, findings, evidence, and reports — is governed by the relevant signed engagement documentation, which may include a Non-Disclosure Agreement, Master Services Agreement, Statement of Work, Rules of Engagement, and, where applicable, a data-processing agreement.

This Website Privacy Policy describes our practices for the public Website only and is not a substitute for the complete data-processing terms of a client engagement.

19

AI and Automated Tools

Rexscot may use AI-assisted tools as part of appropriate internal business and security research workflows, consistent with the AI-assisted reporting principles described in our Vulnerability Disclosure Policy.

We do not claim that every Website submission or communication is processed by AI, that every vulnerability report is sent to an AI provider, or that no human review occurs. Use of AI tools, where it occurs, is limited to appropriate internal workflows.

Rexscot does not send confidential client data or sensitive information to external AI systems outside of a documented, appropriate workflow.

21

Privacy Contact

DetailInformation
Privacy Contactall@rexscot.com
General Contactall@rexscot.com
Websitehttps://rexscot.com

Rexscot does not currently have a dedicated privacy-specific mailbox separate from its general business contact address.

22

Policy Updates

We may update this Privacy Policy from time to time to reflect changes in our practices, the technologies used on this Website, or applicable law. The current version is always published at rexscot.com/privacy.

VersionEffective DateLast UpdatedStatus
1.0[ POLICY EFFECTIVE DATE ][ LAST UPDATED ]Draft

23

Governing / Legal Information

24

Frequently Asked Questions

What information does Rexscot collect?

Primarily what you provide directly through the Contact or Collaborate forms, or by emailing us — see Section 3. We do not run analytics or use tracking cookies.

How can I contact Rexscot about privacy?

Email all@rexscot.com — see Section 21.

How do I report a security vulnerability?

Review the Vulnerability Disclosure Policy at rexscot.com/security and email all@rexscot.com with the appropriate subject line.

Does the Vulnerability Disclosure Policy apply to client systems?

No. It applies only to Rexscot's own published in-scope assets. Client systems require separate written authorisation — see Section 2D of the Vulnerability Disclosure Policy.

How can I request information about my data?

Email all@rexscot.com — see Section 15 (Your Rights) and Section 21 (Privacy Contact).