Public Standard for Good-Faith Security Research, Vulnerability Reporting, Safe Harbour and Coordinated Remediation
| PUBLICATION INFORMATION | PUBLICATION 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 |
|---|
Subkuz welcomes responsible reports from security researchers, readers, technology professionals and members of the public who identify a potential vulnerability affecting an authorised Subkuz service. A clear vulnerability disclosure process improves the security and resilience of digital journalism, protects readers, sources, contributors, employees and commercial partners, and gives the responsible technical team a reasonable opportunity to investigate and remediate an issue before avoidable harm occurs. This page establishes the conditions under which limited good-faith research and coordinated disclosure will be handled.
This page is not a public bug bounty, does not promise payment and does not authorise unrestricted testing. It does not replace contracts, law, regulatory reporting, incident response, privacy obligations or the security rules of a third-party provider. A person who cannot comply with these conditions should not conduct active testing and may report an observed issue without attempting to reproduce it.
A suspected vulnerability should be submitted through the Subkuz Security Vulnerability Report Form or reported 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. The report should identify the affected domain, application, feature, account type or version; explain the issue and potential impact; provide concise reproduction steps; identify any conditions required to observe it; state whether personal data or another sensitive record was encountered; and include safe supporting evidence. Passwords, authentication codes, private keys, unrelated personal data and live exploit payloads must not be sent through ordinary email.
A reporter should provide a reliable contact method if updates or clarification are requested. Anonymous reports may be considered where the information is sufficient, but the absence of a communication channel may limit validation, coordination and recognition. Urgent reports involving active exploitation, source exposure, account takeover, payment compromise, unauthorised publication, election information or substantial personal-data risk should be marked Critical and should explain the immediate evidence rather than using urgency language without support.
This process applies to publicly accessible Subkuz websites, applications and services that are controlled by Subkuz Media Networks Private Limited or an authorised Subkuz operator and that display or link to this page. It includes a production asset only to the extent that the asset is operated as an official Subkuz service. A third-party platform, hosting provider, payment service, advertising provider, social-media account, software vendor, partner publication, employee device, home network, unrelated group company or infrastructure not controlled by the responsible Subkuz entity is outside scope unless it is identified expressly in the live security scope record.
An asset that merely contains the Subkuz name, resolves through a shared provider or is discoverable through a technical scan must not be assumed to be authorised for testing. Where ownership or scope is uncertain, the researcher should report the observation and ask for confirmation before active testing. Subkuz may add, restrict or remove assets from scope according to ownership, operational status, risk and third-party obligations.
Good-faith research is limited to activity reasonably necessary to confirm and describe a vulnerability while avoiding harm. The researcher must use their own account and data where an account is needed, minimise requests, respect rate limits, stop when the issue is demonstrated, avoid persistence, and use the least intrusive proof capable of supporting validation. Research must not degrade availability, alter published content, interfere with journalism, affect another person, access information beyond what is necessary, or create a risk disproportionate to the value of the test.
A person complying in good faith with this page should act transparently, provide accurate information, preserve confidentiality, cooperate with reasonable validation questions and allow coordinated remediation. Accidental access to another person's data must be reported immediately, and the researcher must stop, avoid further review, retain only the minimum evidence necessary to identify the issue and securely delete the information when Subkuz confirms that preservation is no longer required.
This page does not authorise denial-of-service testing, traffic flooding, resource exhaustion, destructive scanning, malware, ransomware, credential stuffing, password spraying, brute force, social engineering, phishing, spam, physical intrusion, insider recruitment, extortion, threats, payment fraud, purchase manipulation, modification or deletion of data, persistent access, privilege use beyond the minimum proof, extraction of databases, interception of communications, surveillance of another person, bypass of lawful access restrictions for unrelated purposes or testing of a third-party system without its permission.
Researchers must not access confidential newsroom material, source identities, unpublished investigations, grievance files, private messages, financial data, identity documents, health information, precise location or another sensitive record beyond the unavoidable minimum necessary to recognise the vulnerability. A person must not create a public account in another person's name, contact a source or user to prove impact, plant false news, alter an article, publish a synthetic item, change a correction, manipulate an election page or exploit a vulnerability for commercial leverage.
Where a researcher acts in good faith, complies with this page, remains within authorised scope and promptly reports the vulnerability, Subkuz will not initiate civil action or request a law-enforcement investigation solely because of the compliant research. If a concern arises about whether a planned action is permitted, the researcher should request written clarification before proceeding. This commitment does not authorise conduct prohibited by law, does not waive rights concerning unrelated or harmful conduct and does not bind a third party, regulator, law-enforcement body, service provider or other rights holder.
A person who exceeds the minimum necessary testing, conceals access, retains or uses data, demands payment through threats, causes disruption, exploits the issue after reporting, publishes sensitive information prematurely or acts outside the stated scope cannot rely upon this commitment. Subkuz may preserve evidence and take appropriate legal, technical or protective action where conduct creates a material risk or appears malicious.
Subkuz aims to acknowledge a sufficiently detailed report within three business days and to provide an initial triage status within ten business days. These are service targets rather than guaranteed legal deadlines. Time may vary according to severity, clarity, system ownership, language, third-party coordination, holidays, active incidents and the complexity of safe reproduction. Acknowledgement does not confirm that the issue is valid, unique, exploitable or within scope.
The security team may request logs, timestamps, affected versions, account identifiers, screenshots, a screen recording, a minimal proof or clarification of expected and observed behaviour. The reporter should not expand testing merely because additional detail is requested. Where the report is valid, Subkuz may provide periodic status updates and may coordinate with Subkuz Media Networks Pvt Ltd ( SMN ), an authorised operator, a service provider, CERT-In or another competent party according to responsibility, confidentiality and law.
Subkuz assesses severity according to exploitability, privileges required, affected data, source and newsroom risk, user interaction, scale, persistence, availability, integrity, confidentiality, public-safety impact and evidence of active exploitation. A technically interesting issue may have low practical impact, while a narrow vulnerability involving confidential sources, publication integrity, election information or account control may require urgent action. Severity and remediation priority remain accountable operational decisions rather than rewards determined by the reporter.
Remediation may include a code change, configuration change, access restriction, temporary feature suspension, credential rotation, monitoring, user notification, vendor action, compensating control or acceptance of a residual risk supported by a documented assessment. Subkuz does not promise a fixed repair date for every issue, but valid exploitable vulnerabilities will be addressed according to risk and available safe mitigation. A report may be closed where it is not reproducible, is an intended behaviour, requires unrealistic conditions, concerns an unsupported third party or presents no meaningful security impact.
The reporter must not publish vulnerability details, exploit code, affected data or identifying evidence before Subkuz has had a reasonable opportunity to validate and remediate the issue. The ordinary coordinated-disclosure period is ninety calendar days after Subkuz confirms a valid report, unless the parties agree to another period or an urgent public-safety reason requires a different approach. Complex supply-chain issues may require more time, while active exploitation may require earlier protective communication. Silence, delay or disagreement does not authorise disclosure that would expose readers, sources or systems to avoidable harm.
Public disclosure should describe the issue accurately, avoid personal data and operational secrets, identify the remediation status and preserve agreed credits. Subkuz may publish a security advisory, vulnerability note, acknowledgement or technical explanation where this supports affected users and public confidence. The reporter must not use the Subkuz name, logo or communication to imply employment, partnership, certification or endorsement.
Subkuz may acknowledge a researcher publicly with the researcher's permission where a valid report materially improves security and recognition does not create a safety, privacy, legal or operational risk. The form and timing of acknowledgement remain subject to coordinated disclosure and the interests of affected persons. Duplicate reports may be recognised according to the earliest sufficiently actionable submission rather than the earliest incomplete message.
This page does not create a bug bounty, employment relationship, procurement commitment, licence fee or entitlement to payment, gifts, travel, publicity, merchandise or future work. A reward exists only where a separate written programme or agreement states the scope, eligibility, amount and conditions. A demand for money or benefit as a condition of withholding harmful disclosure is inconsistent with responsible research and may be treated as a security and legal matter.
Reports and supporting evidence may contain contact information, technical identifiers, account data, logs, screenshots and vulnerability details. Subkuz processes that information for validation, remediation, security, legal compliance, communication, recognition and defence of rights according to the Privacy and Data Protection Policy. Access is restricted to authorised personnel and providers whose participation is necessary. Vulnerability information may be shared with affected vendors, authorised operators, CERT-In, regulators, law enforcement or other competent parties where necessary and lawful.
A reporter must redact unrelated personal data and must not submit a full database, mailbox, source file, credential set or private document merely to prove access. Subkuz may request secure transfer through another channel for material that cannot be sent safely by ordinary email. Records are retained according to incident, security, legal and regulatory requirements and may be subject to preservation where an investigation, audit, claim or statutory reporting duty applies.
A vulnerability report is distinct from a confirmed cyber incident, although the same matter may become both. Subkuz and its responsible technology and operating entities maintain separate procedures for incident containment, evidence preservation, legal assessment, notification and coordination with competent authorities. Nothing in this page limits a duty to report an applicable incident within a statutory period, maintain required logs, respond to a lawful direction or notify affected persons.
A researcher should contact the relevant emergency or law-enforcement authority where there is an immediate threat to life or public safety. Reporting to Subkuz does not replace a legal duty that applies directly to the researcher or another organisation. Subkuz may coordinate a qualifying vulnerability with CERT-In under its responsible vulnerability disclosure and coordination process where that is appropriate to the affected product, vendor or national cybersecurity interest.
Subkuz maintains a machine-readable security.txt record at https://subkuz.com/.well-known/security.txt. It is served through HTTPS as UTF-8 plain text and contains the current security contact, expiry, canonical location, policy location and preferred language information. The record applies to the domain from which it is retrieved unless an authorised scope statement expressly provides otherwise. It complements this page and does not by itself authorise testing.
Researchers must verify that the security.txt record, this page and any requested transfer route are served through an official Subkuz domain before sending sensitive information. Subkuz personnel will not ask a reporter to provide passwords, authentication codes, private keys, unrelated personal data or payment in order to submit a report. A message from an unverified personal account, social-media profile or unrelated domain must not be treated as authority to test a system or disclose data. Suspicious requests should be verified through [email protected].
A concern about the handling of a vulnerability report may be sent to [email protected] with the original reference and a clear explanation of the issue. A disagreement about severity, reward, recognition, remediation or disclosure does not create a right to access additional systems or publish protected information. Subkuz may obtain an independent technical, privacy or legal review where a material conflict or high-impact dispute exists.
This page is reviewed at least annually and earlier after a serious incident, material legal change, substantial technology change or significant failure of the disclosure process. Changes to authorised scope or contact information may take effect immediately for safety reasons. Material public changes are recorded through the Subkuz Public Policy Change Log. Researchers are responsible for consulting the current version before testing.