What is the typical response timeline?

3-6 weeks for most deficiency packages - depends on the number of items, retesting scope, and how much of the original submission needs reconstruction. Our fastest reviewer-ready package was 11 days from engagement to filed response (Class II connected wearable, RTA citing inadequate Section 524B documentation).

What if we have under 30 days of clock left?

Escalate immediately - engagement letter signed in 24 hours, gap analysis next business day, parallel work streams from day 3. We have shipped reviewer-ready packages in under two weeks when the path is straight (mostly documentation gaps, no major retesting). When retesting is required and time is tight, sometimes the right call is a small interim filing followed by a more complete second response - we help decide that.

Is the 24-hour gap analysis paid?

It's the first paid deliverable of the engagement and becomes the foundation for the fixed-fee remediation work. You get a written gap analysis plus a fixed-fee quote for the full response package within two business days - so the 180-day clock is not burning while you wait for scoping.

Can you take over a response another vendor started?

Yes. We do mid-engagement transitions when an existing vendor is not delivering. The first deliverable is a gap analysis of what they have produced vs what the reviewer asked for, then we bridge the gap. Honest assessment up front - sometimes finishing what they started is faster than rebuilding.

Do you file the response or do we?

Either. Most clients prefer that we deliver the complete reviewer-ready package and their internal RA team handles the actual eSTAR upload. We can also coordinate directly with your filing consultant. Deliverable format is the same.

How is De Novo deficiency response different from 510(k)?

510(k) responses lean on the predicate-comparison narrative; De Novo responses lean on security-architecture justification because there is no predicate. PMA responses involve cross-discipline coordination. IDE responses focus on study-subject safety arguments.

What happens if the reviewer rejects the second-cycle response?

Third cycle starts on the same 180-day clock. Rare with a properly structured response, but if it happens, the third response builds on the second-cycle reviewer feedback specifically - which is usually narrower than the original deficiency letter.

Will retesting be required?

For most pen-test deficiencies, yes - either to extend scope or to validate fixes. We scope retesting tightly to the deficiency, not the whole engagement, so cost and time are bounded.

How do you avoid creating new deficiencies in the response?

Every artifact change is run through the eight-artifact consistency check (see our premarket checklist). New trust boundaries in the threat model are reflected in the architecture views; new SBOM entries get vulnerability triage; new pen test scope gets a Letter of Attestation.

What is the single fastest way to slow down a response?

Argue with the reviewer. The response document should address the deficiency directly with new evidence; framing-disputes about whether the deficiency was reasonable extend the cycle every time. Save those for the post-clearance lessons-learned.

FDA Cybersecurity Deficiency Letter Response Playbook

On this page

By Christian Espinosa, MBA, CISSP

Founder & CEO · Blue Goat Cyber

Key Takeaways

Triage in 24 hours: identify which deficiencies need rebuilt artifacts vs updated artifacts.
A reviewer-ready response is point-by-point, traces back to the original submission, and produces evidence the reviewer can verify in 30 minutes.
Most deficiencies cluster in three patterns: thin threat model, incomplete pen test, weak postmarket plan. Plan fixes accordingly.
A 24-hour gap analysis converts panic into a fixed-fee timeline before the 180-day clock burns.

Pillar Guide · Updated 2026 · 22 min read

Talk to a MedTech cybersecurity expert

The first 24 hours

When the deficiency letter arrives, the 180-day clock is already running. Within 24 hours you should know:

Which deficiency items need full artifact rebuilds (e.g., new pen test) and which need updates (e.g., add a missing architecture view).
Which items have data dependencies (need engineering work) vs documentation dependencies (need writing).
Whether retesting is required and on what scope.
A realistic timeline with milestone gates.

Triage: read the letter the way reviewers wrote it

Reviewers reference specific guidance sections. Map each deficiency item to the section it cites and the artifact it implicates. Group items into categories:

Artifact missing entirely (rebuild from scratch).
Artifact present but inadequate scope (extend or rerun).
Artifact present but inconsistent with another artifact (reconcile).
Documentation gap (write the missing narrative).
Traceability gap (build the missing matrix entries).

The three deficiency patterns we see most

1. Thin threat model

STRIDE present but not per element, missing architecture views (almost always multi-patient harm or updateability), no traceability matrix. Fix: rebuild the threat model with the four views and the traceability matrix. Time: 3-5 weeks.

2. Incomplete pen test

Scope did not cover full attack surface (cloud or wireless typically), no Letter of Attestation, or methodology was black-box. Fix: scope the missing surface, retest, produce the Letter. Time: 4-6 weeks for the missing surface plus retest of high/critical fixes.

3. Weak postmarket plan

Plan describes intent but not cadence, SLAs, or named owners. Fix: rewrite with monitoring sources, triage SLA, patch cadence, CVD intake, and EOS tracking. Time: 1-2 weeks.

The reviewer-ready response format

A response that gets through second-cycle review without a third cycle has a specific structure:

Cover letter - identifies the submission, the deficiency letter date, and the response date.
Point-by-point response document - each deficiency item quoted verbatim, response narrative, references to updated/new artifacts.
Traceability matrix - deficiency item → response → artifact location.
Updated artifacts - rebuilt or extended threat model, pen test report, SBOM, postmarket plan, etc.
Letter of Attestation - if pen test was redone or extended.
Reviewer-eye narrative - one-page summary the reviewer can read first to orient.

Pathway-specific considerations

510(k) AI letter

Focused on substantial-equivalence-relevant cyber items - threat model alignment to predicate, SBOM completeness, pen test scope. Predicate-comparison narrative is often the missing piece.

De Novo deficiencies

Often probe novel risk arguments and security-architecture justifications. Response needs to strengthen the architecture rationale, not just add documents.

PMA deficiencies

Deepest documentation, full design history file traceability, and frequently coordinate with non-cyber reviewers on risk control and human factors. Response should explicitly address cross-discipline integration.

IDE Clinical Hold (21 CFR §812.42)

Focus on whether unresolved cybersecurity risks could expose study subjects to unreasonable risk. Response demonstrates threat model coverage of the clinical environment, security risk assessment, and any compensating controls before enrollment proceeds.

How fixed-fee response works

After the 24-hour gap analysis, you receive a fixed-fee quote covering: rebuilt or extended artifacts, retesting where required, point-by-point response document, traceability matrix, and reviewer-ready package. Includes one revision pass if the reviewer comes back with follow-up questions; new deficiencies on second cycle are handled under a separate engagement (rare with this approach).