CERT-In reporting clock
CERT-In's April 2022 directions require cyber incidents to be reported within 6 hours of noticing them. A flaw found and fixed through your programme never needs to become an incident.
Vetted researchers find the flaws. We triage every report, so your developers only see real ones.
XcellHost runs your vulnerability reward programme end to end. We write the scope, safe-harbour terms and disclosure policy, invite vetted researchers, validate each report in an agreed window, track the fix, retest it and pay rewards from a pool you fund.
Independent security researchers test public websites, APIs and mobile apps every day. Without a published channel, the ones who find something either stay quiet, email a support inbox that nobody triages, or post it online. A managed bug bounty turns that into a controlled programme: written scope, written rules, a safe-harbour promise for good-faith testing, and rewards paid only for valid, unique findings.
XcellHost runs it for you. We write the policy, choose and vet the researchers, run 24×7 intake, reproduce and rate every report, remove duplicates and noise, and send your developers a clean ticket with a fix suggestion. When the fix is in, we retest it, pay the reward from your pool and handle disclosure on the terms you agreed.
UPI-linked apps, customer portals, partner APIs and D2C storefronts ship every week. An annual test checks one version on one date. A standing programme keeps many testers looking at the version that is live.
CERT-In's April 2022 directions require cyber incidents to be reported within 6 hours of noticing them. A flaw found and fixed through your programme never needs to become an incident.
The Act expects reasonable security safeguards for personal data, with penalties of up to ₹250 crore for failing to take them. Continuous outside testing is evidence that you looked.
CERT-In runs a responsible vulnerability disclosure process and aims to close coordinated cases within about 120 days. Your programme gives researchers a faster, direct route to you.
Rewards are paid only for valid, unique, in-scope findings. Scanner output, duplicates and out-of-scope reports cost you nothing and never reach your developers.
Regulatory figures summarised for context. Confirm current obligations with your legal and compliance team.
Most organisations begin with a private, invite-only programme. Pick a model to see how the researcher pool, report volume and noise change.
A small cohort of vetted researchers, chosen for your technology, tests a defined scope for rewards. Volume stays manageable while your team learns the fix rhythm.
Researcher counts are illustrative and depend on scope and technology. A VDP can run alongside any bounty.
Scope is the most important page of the programme. It protects your production systems and tells researchers exactly where safe harbour applies.
Who does what, from policy to disclosure. The filled marker shows who leads each phase; the ring shows who takes part.
Asset list, out-of-scope list, testing windows, reward table, safe-harbour wording and disclosure model, signed off by you.
Invite-only cohort matched to your stack. NDA and programme terms accepted; identity verified for payouts.
Small cohort, narrow scope first. We watch volume and your fix speed before widening.
24×7 intake. Scope and duplicate checks, reproduction in an agreed window, severity rated on a CVSS-style scale.
Clean ticket into your tracker with impact and fix guidance. We retest when you say it is fixed.
Reward paid from your pool, disclosure on agreed terms, monthly report and board summary.
A bounty only works when both sides know the rules. Every programme starts with documents, not testing.
Developers get tickets they can act on. Leadership gets a monthly picture of risk found, fixed and paid for.
Reproduction notes, affected asset, impact, severity and a fix suggestion. Sample: "Finding #12 · public storage bucket · High · fixed in 48 h (sample)".
One page for the board: findings by severity, time to fix, spend against pool, trend.
Target fix times by severity, owners, overdue items and exceptions you accepted.
Every fix re-checked by XcellHost before closure, with a dated record for auditors.
Who was paid, for which finding, from which tier — reconciled against your pool every month.
Reports received vs valid, noise filtered, root-cause themes and the scope we recommend next.
A bounty programme helps you meet these expectations. It does not by itself make you compliant, and it does not replace the audits your regulator requires.
Summaries for orientation only. Confirm the current text of each direction or framework with your compliance team.
Mobile apps and APIs change weekly. Researchers focus on account takeover, payment logic and authorisation flaws that scanners miss.
Start with a private programme on non-core portals and partner APIs, then expand as your change process keeps pace.
Sale seasons bring new code and new attackers. Researchers look at coupon abuse, account flaws and exposed order data.
Enterprise buyers ask whether you run a vulnerability programme. Tenant isolation and API authorisation are the usual focus.
Health records are sensitive personal data. Scope excludes real records; researchers work on seeded test patients only.
Private, tightly scoped programmes on staging builds before go-live, with non-disclosure as the default.
XcellHost's fees cover policy, researchers, triage, retest and reporting. The reward pool is funded by you and paid out only for valid findings; unused balance stays with you.
*Indicative placeholder prices · excl. 18% GST · to be confirmed with XcellHost. Reward pool is on quote and is not charged online.
Set your scope, how mature your security already is and how competitive your reward table should be. The planner estimates valid findings and the pool to fund. Estimates are illustrative.
Illustrative model: finding rates and reward amounts are placeholders, not a forecast. You set the final reward table.
Tick what researchers may test and how you want findings handled. The draft updates as you go; download it to share with your team before a scoping call.
Choose how many programmes and how many months. The reward pool is quoted separately and never charged online.
A bounty complements penetration testing; regulated entities still need the audits their regulator requires. Pair it with Breach & Attack Simulation to keep detections tested too.
30 minutes on assets, maturity and goals. Use the scope builder to prepare.
Scope, rules, safe harbour, reward table and disclosure model approved by you.
You fund the reward pool; we set up payouts and tracker integration.
Small cohort, narrow scope. Triage and tickets start flowing.
Report, retests, spend against pool, and whether to widen scope.
Your developers see validated findings with a fix suggestion, not raw submissions.
01Critical findings can be escalated to XcellHost Vortex SOC for monitoring while the fix is built.
02Certified security and service management around your reports and data.
03Researcher KYC, payments and the reward ledger run by us, billed to you in INR.
04Azure, Microsoft 365 and Entra fixes guided by one partner.
05Mumbai managed cloud and security for more than two decades.
06