DOC #067 02_PUBLIC_WORKING_FORMS

SUBKUZ SECURITY VULNERABILITY REPORT FORM

Subkuz Global Governance Framework | Issued by Subkuz Media Networks Private Limited (CIN: U72900JH2020PTC014521)

Document #067 | Verified Master Version

Public Form for Good-Faith Reporting and Coordinated Disclosure of Security Vulnerabilities

FORM INFORMATION FORM INFORMATION
Issued by Subkuz Media Networks Private Limited
Corporate Identification Number CIN U72900JH2020PTC014521
Effective date 6 August 2026
Last reviewed 6 August 2026
Previous legal name during statutory disclosure period Subkuz Media Networks Private Limited

1. Purpose, responsible testing and scope

Use this form to report a suspected vulnerability affecting an authorised Subkuz website, application, domain, account service, interface, application programming interface, server, cloud environment, communication system or other asset identified as within scope by the Security Vulnerability and Responsible Disclosure Page. The form supports good-faith technical reporting, internal triage, remediation and coordinated disclosure. It does not authorise activity that is unlawful, destructive, deceptive, outside published scope or unnecessary to demonstrate the issue.

A reporter should stop testing once sufficient evidence exists, avoid accessing or retaining unnecessary personal or confidential data, avoid service disruption, social engineering, credential theft, malware deployment, physical intrusion, extortion and threats of premature disclosure. Subkuz's limited good-faith commitment applies only to activity that remains within the published responsible-disclosure conditions and applicable law. Submission does not create employment, a contract, entitlement to payment, a bounty, public credit or immunity from third-party action.

2. Reporter and secure communication

Field Information to provide
Name, organisation or chosen researcher identifier
Email address or secure contact method
Country and time zone
Preferred attribution if public credit is later considered [ ] Full name / [ ] Researcher handle / [ ] Organisation / [ ] Anonymous / [ ] Discuss before any public attribution
Encryption or secure communication preference
Whether another coordinator, vendor or authority is involved

3. Affected asset and discovery

Field Information to provide
Affected domain, host, application, endpoint or component
Application version, build or environment
Date and time first identified
Date and time last reproduced
How the asset was identified as belonging to Subkuz
Whether the asset appears in published scope [ ] Yes / [ ] No / [ ] Unsure; scope confirmation requested
Account type or permission level used
Security policy or security.txt location consulted

4. Vulnerability description and impact

Field Information to provide
Vulnerability category [ ] Authentication or session management / [ ] Authorisation or access control / [ ] Injection or code execution / [ ] Cross-site scripting or content injection / [ ] Data exposure or privacy / [ ] File upload or path handling / [ ] Cryptographic or transport issue / [ ] Business logic / [ ] API or mobile application / [ ] Configuration or cloud exposure / [ ] Supply-chain or dependency / [ ] Other: __________________________________________
Plain-language summary
Technical description
Potential impact
Affected users, systems or data categories
Conditions or privileges required
Suggested severity and reasoning
CVE, CWE, vendor or other identifier, if known
Evidence of active exploitation or public exposure

5. Reproduction and proof

Field Information to provide
Prerequisites and test account details, without passwords
Step-by-step reproduction
Expected secure behaviour
Observed behaviour
Evidence available [ ] Screenshot / [ ] Screen recording / [ ] Sanitised request and response / [ ] Proof-of-concept code / [ ] Log or trace / [ ] Hash or file reference / [ ] No attachment / [ ] Other: __________________________________________
Reliability of reproduction [ ] Reproduces consistently / [ ] Intermittent / [ ] Reproduced once / [ ] Not reproduced after initial observation

Evidence should be sufficient to permit verification without exposing live secrets or unnecessary personal data. Do not place passwords, private keys, session tokens, complete personal records, unpublished source material or exploit code enabling immediate mass abuse into an ordinary attachment. State that such material exists and request a safer transfer method. Where possible, redact or replace real records with controlled test data while preserving the technical condition.

6. Data access, actions and containment

Field Information to provide
Personal, confidential or source data encountered
Quantity and type of data viewed or retained
Steps taken to minimise, protect or delete the data
Changes made to accounts, content, settings or systems
Service disruption or performance effect observed
Whether exploitation by another actor is suspected
Immediate containment recommendation

A reporter should not download a full dataset, access additional accounts or continue escalating merely to demonstrate severity. If accidental access to sensitive information occurs, stop, preserve only the minimum evidence necessary, protect it from further disclosure and describe the incident promptly. Subkuz may provide instructions for secure deletion, evidence preservation or communication with an affected vendor or authority.

7. Disclosure status and coordination

Field Information to provide
Other parties already notified
Public disclosure already made [ ] No / [ ] Yes. Identify where and when: ______________________________
Planned disclosure date or deadline
Reason for the proposed timeline
Whether a vulnerability identifier has been requested
Whether coordinated disclosure support is requested
Potential third-party vendor or dependency
Preferred coordinated-disclosure outcome

Subkuz ordinarily seeks coordinated disclosure and may request a reasonable remediation period, commonly up to ninety days depending upon severity, active exploitation, vendor dependencies and public risk. That period is not an automatic restriction on lawful speech and may be shortened or extended through good-faith coordination. A reporter should identify an urgent public-interest reason before disclosing an unremediated issue that could enable harm.

8. Research conduct and declaration

Field Information to provide
Testing methods used
Automated scanning or tooling used
Social engineering, physical access or third-party accounts used [ ] No / [ ] Yes. Explain fully: _________________________________________
Payment or bounty requested [ ] No / [ ] Recognition only / [ ] Payment requested but not made a condition of non-disclosure / [ ] Other: __________________________________________
Conflict, employment or commercial relationship with Subkuz or a vendor

By submitting this form, the reporter confirms that the report is made in good faith, the description is accurate to the best of their knowledge, testing was limited to what was reasonably necessary, evidence has not been fabricated, no threat or extortion has been used, and unnecessary personal data will not be retained or published. The reporter understands that Subkuz may share technical details with authorised group entities, processors, vendors, legal advisers, insurers, coordinators or competent authorities where necessary to investigate and remediate the issue, while seeking to protect the reporter's identity and data proportionately.

9. Submission and acknowledgement

Field Information to provide
Reporter name or identifier
Signature or electronic confirmation, optional
Submission date and time zone
Safe acknowledgement route
Attachments or secure-transfer items listed

Submit through the official Subkuz Security Vulnerability Report Form or send a report to [email protected]. If the dedicated route is unavailable, a non-sensitive initial notice may be sent to [email protected] with the subject Security Vulnerability. Place no live secret, private key, authentication token, complete dataset, unpublished source material or immediately weaponisable exploit in ordinary email. A sufficiently detailed report is recorded and receives a security reference through the safe contact route supplied. Subkuz aims to acknowledge it within three business days and provide an initial triage status within ten business days. The reference confirms receipt only and does not confirm validity, severity, reward, public credit or a fixed remediation date.