Scale the capacity. Keep the control.

A dedicated, ring-fenced cyber security delivery pod in India, operated by Codec Networks for one client, that performs recurring cyber work (product support, vendor risk and compliance evidence, SOC triage, VAPT retests, incident documentation) inside the client's tools and access model, to the client's SOPs and SLAs, with QA on every output and a governance cadence from daily operations to a quarterly steering committee.

Staff augmentation supplies people to a queue; the client manages them and owns the quality. A pod is an operating model: Codec Networks designs the process, builds SOPs and QA, measures SLAs, provides tower leads and a programme manager, and reports to a steering committee. The difference shows in consistency, auditability and the backlog.

Those services are delivered on Codec Networks' platforms and methods under its own brand. A pod works in the client's platforms to the client's methods, as capacity within the client's or partner's operation, including white-label delivery for consulting firms and MSSPs. Many clients use both.

Five service lines: product-centric cyber operations (L2/L3 support, deployment validation, configuration review, health checks); TPRM and GRC operations (questionnaires, evidence review, scoring, gap tracking, portfolio reporting); SOC and MDR back-office (alert triage, investigation support, reporting, tuning); VAPT and secure engineering back-office (remote testing, retests, API and code review support, vulnerability tracking); and forensics and incident support (intake, timelines, evidence indexes, RCA notes, post-incident reports).

It does not make the client's decisions. Production changes, blocking actions, account disabling, containment, risk acceptance and regulatory or customer-facing commitments remain with the client unless explicitly delegated in writing. It does not guarantee breach prevention or detection of all threats, and it does not provide legal, regulatory, underwriting or certification opinions.

A starter pod is three to five people; a pilot pod five to eight; a managed pod fifteen to thirty; a strategic pod thirty or more. Size follows service line, volume, coverage hours, language and tool complexity, and is adjusted on data at the steering committee.

Discovery and contracts in weeks one and two, access and onboarding design in weeks three and four, team onboarding, SOPs and training in weeks five and six, and pilot operations from week seven. The pace depends on the client's access provisioning and process owner availability.

Yes. Business-hours coverage follows the client's time zone where agreed; an Indian pod covers European mornings and North American evenings in its own working day; shift coverage extends to 24×7 as the pod scales.

In the client's own systems by default. Codec Networks personnel reach it through approved, monitored, role-based channels (SSO, MFA, least privilege, secure VDI or an approved access channel), and only agreed work outputs are stored or exported, under the DPA and SOW. Codec-owned or hybrid tooling is used only where security, contract and data-residency needs allow.

Through an access matrix approved by the client's security team, with SSO and MFA, RBAC, least privilege, periodic access reviews on an agreed schedule and immediate revocation on exit or role change. Access, task, ticket and admin logs are kept and reviewed.

No unauthorised local storage. Secure VDI or approved channels, restricted downloads, DLP controls and masking where possible are part of the secure workspace design, and the compliance liaison checks adherence.

Codec Networks applies its own pre-employment screening under its ISO/IEC 27001 certified controls. Customer-requested additional background checks are arranged and charged as agreed in the SOW.

Where personal data is processed on the client's behalf, Codec Networks acts under the DPA as the client's processor, with safeguards, breach notification support and return or deletion on exit. The DPDP Rules, 2025 and GDPR Article 28 are mapped as general guidance; the client and its counsel determine applicability.

Yes. Audit rights are agreed in the MSA. SOPs, access reviews, QA records, logs and SLA reports are maintained so that the client's internal audit, external auditor or regulator can examine how outsourced work is controlled.

The security addendum defines notification timelines, investigation and remediation. Codec Networks' own incident process, run under ISO/IEC 27001, applies, and the client is notified within the agreed window with the evidence needed for its own CERT-In, DPDP or other reporting.

Only under customer-approved AI governance rules. AI-assisted report drafting and QA is an optional add-on with human review on every output; no client data is placed in public AI tools without written approval.

Definitions of done for every work type, SOPs and playbooks, a QA checklist, QA sampling, two-person integrity for sensitive outputs, calibration sessions across analysts and tower leads who validate outputs. Quality is an SLA category with a defect rate and QA pass rate reported weekly.

The client's, by default: its ticketing, SIEM, EDR, GRC, scanning and repository tools. Codec tools or a hybrid model are used where agreed. A tool administrator manages permitted access, dashboards and reporting extracts.

Only with the client's approval or an explicit written delegation with limits. By default the pod triages, investigates, documents and escalates within SLAs; containment, blocking and account actions remain with the client.

Yes. Co-branded or white-label reporting is an add-on for consulting firms and MSSPs, with Codec Networks' QA review before release and the client's rules of engagement governing every test.

Documented handover notes at every shift change, backup resources for every role, SOPs that survive staff changes and an escalation path for blockers. Continuity is part of the secure delivery architecture and the maturity assessment.

Ticket volume, backlog and ageing, acknowledgement, triage and closure performance, exceptions, quality metrics, access-review status and risks, per service line, in the client's template or portal.

Through the escalation rules in the SOP pack: severity-based routes, named client contacts, acknowledgement SLAs and an out-of-band channel. Critical items are escalated immediately, not held for the weekly review.

Yes, on data. Volumes outside the agreed baseline trigger a commercial change request; the steering committee decides on scale, scope and shift changes quarterly, and the maturity assessment records the trend.

A 90-Day Discovery Pilot is a fixed fee. Pilot and managed pods are priced per FTE per month by role band (L1, L2, L3, L4, programme manager), with a set-up fee, or per shift or per assessment where that fits better. Managed and strategic models add SLA and outcome-linked components, annual escalation and, for strategic SPVs, productivity gain-share. Rates are quoted in the proposal and SOW.

Taxes, client-specific tools and licences, travel and on-site work, premium threat intelligence feeds, customer-requested background checks, foreign legal review, local entity costs, cloud consumption and out-of-scope emergency work, unless expressly included in the SOW.

An NDA, MSA, SOW, DPA, SLA, security addendum and applicable schedules. Billing is monthly in advance for FTE and retainer models and by milestone for fixed pilots.

Where agreed, yes: capped, and applying only to confirmed SLA misses attributable solely to Codec Networks, as defined in the SLA.

Daily operations reviews, a weekly review of SLA, backlog, quality and risks, a monthly service review with the performance report, a quarterly steering committee for scope, scale, automation and contractual issues, and an annual review for commercials, renewal and roadmap. Decisions are recorded in the steering pack.

A transition closure report sets out pilot findings, lessons learned, the productivity baseline, a scale recommendation and a maturity roadmap. The steering committee decides whether to move to a 1-Year Pilot SPV, a Managed SPV or to stop.

Termination rights, notice period, transition assistance, access revocation and data return or destruction are defined in the contract. Codec Networks provides handover notes, SOPs and knowledge transfer so that the work can move back in-house or to another provider.

Client data and client-specific outputs, including SOPs written for the client's processes, remain the client's. Codec Networks retains its tools, templates, methods, workflows, playbooks and pre-existing intellectual property.

Cyber security product companies; banks and financial institutions; fintechs and payment platforms; insurers and the cyber insurance ecosystem; MSSPs and MDR providers; consulting and audit firms; healthcare, manufacturing and other large enterprises with continuous cyber workloads.

Codec Networks does not give legal opinions. As general guidance, RBI's Master Direction on Outsourcing of IT Services (April 2023), RBI's IT Governance direction (November 2023), SEBI's framework (August 2024), IRDAI's guidelines (April 2023) and the EU's DORA (applying January 2025) describe due diligence, contracts, access, monitoring, audit rights and exit for outsourced services. The pod's design, contracts and records are built to support those expectations; the client's compliance team determines what applies.

Yes. ISO/IEC 27001:2022 controls 5.19 to 5.22 and SOC 2 criterion CC9.2 concern supplier relationships and monitoring; the access matrix, SOPs, QA records, access reviews and SLA reports are the evidence those controls expect. Codec Networks is itself ISO/IEC 27001:2022 certified.

SOC and incident support pods produce the documentation (intake notes, timelines, evidence indexes) that the client's six-hour CERT-In reporting under the Directions of 28 April 2022 depends on, within the client's templates. The client files the report; the pod supplies the facts on time.

Yes. Pods are often one tower within a larger operation, taking over a queue, a shift or a service line, with SOPs and handovers agreed with the existing team.

Yes. The 90-Day Discovery Pilot is designed for it: a process map, an access assessment, a trial team on a sample of the work and a scorecard, for a fixed fee, before any multi-year commitment.

Process owners and contacts; timely access to tools, systems, documentation and tickets; authorised scope, roles, escalation contacts, data handling rules and approval workflows; licences or approval of Codec-provided tools; and decisions on risk, production changes and regulatory submissions, which remain the client's.

Confirm the preferred service line and operating model; hold a discovery workshop on process, tools, volumes, SLAs, access and data protection; receive a final SOW with resource plan, timeline, commercials and governance; execute the NDA, MSA, SOW, DPA, SLA and security addendum; and begin transition, onboarding and pilot execution.