GxPlex

FDA device cybersecurity

Cybersecurity in Medical Devices — Quality System Considerations and Content of Premarket Submissions

Recorded status
superseded (basis: tool-read)
Last person check
— not yet verified
Last observation
Retained text
nothing held — The prose this record retains for this entry was extracted only from records classified as something other than the document it names, so there is nothing here a quotation from this document could be checked against.

3 corrections name this row · last → history

Evidence coverage#

Of the 12 rungs of this entry’s evidence ladder: 4 held · 1 held in part · 2 read, and not there · 5 nothing held.

The 12 rungs, each with its mark
  1. identity — held
  2. publisher — held
  3. jurisdiction — held
  4. type — read, and not there
  5. current edition — nothing held
  6. publication date — nothing held
  7. lifecycle signal — nothing held
  8. publisher notices — read, and not there
  9. observation history — held
  10. text — nothing held
  11. diff — nothing held
  12. verification — held in part

A rung marked nothing held has no recorded reading; one marked read, and not there has a reading that ran and did not find it. Rungs stand in the ladder’s fixed order and the counts in this fixed order of marks: held · held in part · read, and not there · nothing held; neither order says anything about this entry. The counts on /coverage are counted by rules of their own, so a rung here and a count there of one name can differ. The sentence behind each mark is in the evidence ladder, under Evidence.

What this record does not establish#

No conclusion is drawn from absence. An absence here is not evidence that a document does not exist, is not in force, or does not govern.

Of the 12 rungs on this entry, 4 are held, 1 are held in part under a limit each one states, and 7 cannot be established from what this record holds. Each of those carries the reading that produced it and whose blank it is. Ordered by whose blank each names: this record’s own first, then the publisher’s, then the blanks this record cannot attribute at all.

  1. type the publisher’s own surface the class the document calls itself, quoted from its own title The title was read and it does not call this document a regulation, a guidance or a standard, so no class is recorded.
  2. current edition this record has not looked a statement of which edition or revision this record holds No reading of an edition or revision statement is recorded for this entry.
  3. publication date this record has not looked a date the publisher states for this document No reading of a publication date is recorded for this entry.
  4. lifecycle signal this record has not looked a stage, step or status wording read from a publisher surface No read of a publisher surface for a stage or status wording is recorded for this entry.
  5. publisher notices this record cannot tell which official notices the publisher issued about this document A collection of publisher notices has succeeded and none of the records it holds attaches to this entry.
  6. text this record has not looked prose retained from the retrieved bytes, against which a quotation can be checked The prose this record retains for this entry was extracted only from records classified as something other than the document it names, so there is nothing here a quotation from this document could be checked against.
  7. diff this record has not looked a comparison of two retrievals of this document No retrieval of this document carries a digest, so no comparison of one retrieval with another has been made.

5 this record has not looked — no reading of this rung is recorded here. The blank is this record’s, and it is not evidence about the publisher · 1 the publisher’s own surface — a reading reached a surface the publisher published and what was asked for is not on it, bounded to the surfaces read · 1 this record cannot tell which — what is held does not say whether the blank is the publisher’s or this record’s. This is an absence of an attribution, not a kind of one

Established for this entry: identity · publisher · jurisdiction · observation history. Held in part: verification.

The reading behind every one of those is stated rung by rung in the evidence ladder under Evidence, and the public evidence each was marked from is published in full on this page under Timeline, Publisher neighbourhood, Observation history and Sources.

What this record undertakes for this entry is stated in 6 terms, each answering one question, and each answered for this entry in the coverage contract under Evidence:

  1. Observed cadence: how often this record has reached this entry’s address
  2. Text: public, and retained: whether the publisher’s text is public, and whether prose from it is kept here
  3. Hash: what is digested for this entry, and of what
  4. Status verification: which check this record undertakes for the published status, and which it holds
  5. Lifecycle tracked: which lifecycle facts this record follows for this entry
  6. Known limits: the limits this entry’s own record declares

Overview#

Open primary source (opens in new tab) fda.gov View observation 2026-11-02 · sequence 1

Document status what the publisher asserts, and the status recorded here

Publisher lifecycle field: none captured

No status read is recorded for this entry — this record has not read a publisher surface for its status, which is a fact about this record and not about the publisher. A status read is recorded for 7 of 132 tracked entries, 5 of which banked a passage.

Recorded status: superseded (basis: the act named under Established by)

Verification what a person or a tool has confirmed here, and when

Publisher: US Food and Drug Administration Last checked: not yet verified Last read:

Evidence state what this record holds

not currently retrievable — no retrieval of the document this entry names has produced a digest

How this status is recorded
Recorded
superseded — no as-of date is recorded
Established by
Read from the source by tooling on 7 September 2026. No person confirmed it. A further check by a person is asserted on this row and the verification log does not corroborate that further check, which counts toward no verified total.
Evidence
In Current status on this page.
Published at
This record names no separate surface for the status. The primary source it holds is the primary source (opens in new tab). This entry's record is published in machine form at /api/v1/instruments.json.

Filed core. For that label this archive undertakes to close an entry's open status question by rule on a clock, with its reason, and to re-read a ratification on record against its observation every night. The label records what this archive undertakes for a class of entries. It states no finding about this one, and it is not a ranking.

Read from the source by tooling (tool-read), not confirmed by a person. This publisher states no status a machine can read; the value comes from the document's own text. It is excluded from the "verified by a person" count on the board.

Resolution: direct document

What this archive can and cannot establish about this entry. What this row hashes is the successor's page. All 49 observation records ask the URL recorded above — FDA's June 2025 slug, `cybersecurity-medical-devices-quality-system-considerations-and-content-premarket-submissions` — and all 49 record `redirected: true` with a `final_url` at FDA's February 2026 page, `cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket` (40 bare, 9 carrying a tracking query string). One digest covers all 49, and it is the same digest `fda-device-cybersecurity-2026` carried on its first 24 records, 2026-07-31 to 2026-08-08, before those records were re-scoped to that entry. FDA's structured guidance index holds no row for the URL recorded here — read 2026-08-25 at the retained-index rung of this row's retrieval ladder and recorded there as no statement about this document rather than a statement of none. The 2026-08-08 correction entry for `fda-device-cybersecurity-2026` states that this entry's referent problem stays open and that it needs either its own surface or a ruling. The question is filed and open; no ruling is recorded, so nothing here says whether following the redirect is a defect or a deliberate choice. This account states what the record holds and does not settle that. Account written 2026-08-25; this row carried none before.

Authority
US Food and Drug Administration
Jurisdiction
US
Status
superseded
Effective date
— this record holds no effective date for this entry
Last changed
—
Last verified
not yet verified
Watch cadence
monthly
Crawlable
yes · renders server-side
Text licence
freely reproducible
Primary source
Primary source (opens in new tab) fda.gov
Topics
cybersecurity · medical devices

Timeline#

The dated facts this record holds for this entry. Each line below states what one kind of dated fact amounts to here, and links to the list holding it where this entry has one; the list carries the dates, the words and the addresses they were read from. Nothing is counted twice: where a line states a number, the section it names states none.

What is not published. This build serves 3 address(es) holding a time-ordered list for an entry — a TimeMap in JSON, its link-format sibling and an index — each expanding to one document per tracked entry. What they list is CAPTURES of this entry’s source held at a web archive, carrying that archive’s own capture instants; this record serves no copy of a tracked document, so none of those addresses is one of this record’s, and a capture address is published only where the terms filing recorded for the source host permits it. This entry’s own is at /api/v1/timemap/fda-device-cybersecurity.json. The route set naming them, and what each one answers, is published at /developers.

Change history#

Publisher neighbourhood#

What sits around this entry, counted. Every figure below is drawn from a value already rendered elsewhere on this page; where a count has a list, the count is here and the list stays in the section holding its evidence.

The direct document, and the activity around it what this record’s observations of the document recorded inside a stated window, beside the official signals dated inside the same one
Each row is a window of calendar days ending , the day the source-health block below counts its own window to. Every column between the window and the official signals is drawn from the 1 observation(s) of the document this entry holds in total. An observation is counted here only where the class projection places it on the document this entry names.
Window Observations of the document Of those, carrying a digest Of those, carrying a change Direct document Official signals dated inside it
30 calendar days 1 0 not measured no digest in window not measured
90 calendar days 1 0 not measured no digest in window not measured
365 calendar days 1 0 not measured no digest in window not measured

A window is marked changed where at least one observation of the document inside it recorded a change against the previous one; unchanged where the window holds at least one such observation, at least one of them carries a digest of the retrieved bytes, and none recorded a change; undigested where the window holds observations and none of them carries a digest, so no observation in it could be compared with another; and unmeasured where the window holds no observation at all. The word is shorthand for the three counts printed beside it and adds nothing to them. It is a statement about the window and never about the document outside it, which is why a window reaching back before the first observation says so underneath. A mark is derived from the observations a window holds and never from the days it spans; which days inside this entry’s own window hold none is stated by the coverage sentence in Observation history below.

The first observation of the document this entry names is . These windows reach back before it — 30 calendar days · 90 calendar days · 365 calendar days — so part of the span each names was never watched, and a window with no detected difference inside it says nothing about the days before that first observation.

no digest in window — this window holds observations of the document and not one of them carries a digest of the retrieved bytes, so no observation in it could be compared with another and no difference was measurable either way — what this record does and does not digest for this entry is stated by the hash term in the coverage contract above

No word is attached to the signal count beside it, and none will be. Any word for the size of a count needs either a threshold this record would have authored or a comparison against other entries that would rank the sources against one another; the count and its window are the whole claim. The document column beside it carries a word only because the rule reaching it is printed underneath and can be checked against the counts it stands for.

The last column holds no member on this entry. The zero it holds is named under “Around it” below.

Around it official signals naming this entry, by the class their publisher stated
— 88 of the 88 record(s) the store holds could be tested against this entry, and none names it. That zero is a measurement.
Related sources other entries reachable from this one by a relation a publisher states
0 relation(s) this entry’s own publisher states, 5 citation edge(s) out of its retained text and 0 into it. They reach 5 other entry(ies) this record tracks. Each one is listed with the words that state it and the address they were read from, in the section holding it below.
Related standards which of those entries call themselves a standard, in their own publisher’s word
Of the 5 entry(ies) reached, 3 carry their publisher’s word for a consensus standard, 1 state another class and 1 state none. A related entry is counted as a standard only where that entry’s own record carries the publisher’s word for it, quoted and cited on that entry’s page. Nothing is read from a designator: a title containing the letters of a standards body is not a publisher calling a document a standard. Where an entry states no class, it is counted as stating none rather than as not being one.
Topics record identifiers for publisher-stated values, and the voice each one is in
2 identifier(s), minted by the convention published at /conventions. The values themselves are not listed again here; what this adds is the identifier and the voice it is in. 2 come(s) from a term this document’s own publisher states about it, quoted with its citation lower on this page: topic.cybersecurity · topic.medical-devices.
Before, now and next where the record’s day sits among the publisher-dated facts this entry holds
— This entry holds no publisher-dated lifecycle fact, so no position can be derived. What is absent is a dated statement this record has read.

Next holds the publisher-dated facts this record already carries that fall after the day this record calls today — a stated effective date, a consultation close. Nothing is projected and no step is inferred from a lifecycle: where a publisher has stated no further date, the cell says so, and what is absent is a statement rather than a future.

Subject and class (as stated)

The words this document uses about itself, matched verbatim against its own title. Not a statement of scope, and not a judgment about which organisations or products fall under it: each value quotes the span it was read from and links to where that span was read.

This document does not call itself a regulation, a guidance or a standard, so no class is recorded. It is filed under title states no class.

Citations (within the tracked corpus)

One document's retained text contained a form another document is published under, on the date shown, with the words it was read from. An edge cannot tell the manner of a citation — a document naming another in order to exclude it produces the same entry as one adopting it.

publisher-stated citation relationships — not a regulatory applicability determination The policy, stated once

Cites (as published)

These citations are drawn together on the citation graph, where every row carries the same quote and source.

Family (along publisher-stated edges)

A family forms only along a supersedes, superseded-by or document-history line a publisher prints. A shared title, number, date or prefix forms none. This records what one document's publisher lists about another and states nothing about the relationship between their requirements.

Each edge below is read from the page linked beside it.

Evidence#

Current status#

Recorded as superseded from a read of the primary source by tooling on 7 September 2026; no person confirmed it.

No evidence record is stored for the current status.

Evidence ladder#

What this record holds for this entry, rung by rung, each mark derived from a field, a count or a stored reading. Rungs in the order the record acquires them, from what an entry is to what has been checked about it. The order is fixed; a rung’s position says nothing about any entry.

The 12 rungs, as marked for this entry
  1. held. identity an address that describes this document rather than a list it sits in This record holds an address that describes this document, and the names it is published under.
  2. held. publisher the body that published it The publishing body is recorded as US Food and Drug Administration.
  3. held. jurisdiction the jurisdiction the publishing body belongs to The jurisdiction is recorded as US.
  4. read, and not there. type the class the document calls itself, quoted from its own title The title was read and it does not call this document a regulation, a guidance or a standard, so no class is recorded.
  5. nothing held. current edition a statement of which edition or revision this record holds No reading of an edition or revision statement is recorded for this entry.
  6. nothing held. publication date a date the publisher states for this document No reading of a publication date is recorded for this entry.
  7. nothing held. lifecycle signal a stage, step or status wording read from a publisher surface No read of a publisher surface for a stage or status wording is recorded for this entry.
  8. read, and not there. publisher notices official notices the publisher issued about this document A collection of publisher notices has succeeded and none of the records it holds attaches to this entry.
  9. held. observation history a dated series of what the publisher’s address returned This record holds 1 dated record of this document, of 135 records in its series; the rest are classified as records of something other than the document this entry names.
  10. nothing held. text prose retained from the retrieved bytes, against which a quotation can be checked The prose this record retains for this entry was extracted only from records classified as something other than the document it names, so there is nothing here a quotation from this document could be checked against.
  11. nothing held. diff a comparison of two retrievals of this document No retrieval of this document carries a digest, so no comparison of one retrieval with another has been made.
  12. held in part. verification a person’s check of this entry against the primary source This entry was read from the source by tooling on a recorded day, and no person confirmed it.

✓ held — this record holds it, and the sentence beside it names what from · ✗ read, and not there — a reading ran and did not find it — an absence this record measured · — nothing held — no reading of this rung is recorded — nobody has looked, which is not the same as looking and finding nothing · △ held in part — part of it is held, or it is held under a limit the sentence states

The first rung a reading ran on and did not find: type — The title was read and it does not call this document a regulation, a guidance or a standard, so no class is recorded.

What the evidence states

  • This record holds an address that describes this document, and the names it is published under.
  • The publishing body is recorded as US Food and Drug Administration.
  • The jurisdiction is recorded as US.
  • This record holds 1 dated record of this document, of 135 records in its series; the rest are classified as records of something other than the document this entry names.

What it does not state

  • The title was read and it does not call this document a regulation, a guidance or a standard, so no class is recorded.
  • No reading of an edition or revision statement is recorded for this entry.
  • No reading of a publication date is recorded for this entry.
  • No read of a publisher surface for a stage or status wording is recorded for this entry.
  • A collection of publisher notices has succeeded and none of the records it holds attaches to this entry.
  • The prose this record retains for this entry was extracted only from records classified as something other than the document it names, so there is nothing here a quotation from this document could be checked against.
  • No retrieval of this document carries a digest, so no comparison of one retrieval with another has been made.
  • This entry was read from the source by tooling on a recorded day, and no person confirmed it.

Evidence states#

All 8 evidence states, marked against this entry’s own fields. The axis at the top of this page publishes the first of them this entry meets; a state it meets after that is marked as met and not carried, because a state an entry meets and does not carry is not the same fact as one it fails. 7 of the 8 come from the published model and 1 was recorded here. The order, and why it is not a ranking, is stated on the observatory.

  1. not a document not met a body, committee or programme — there is no document here to retrieve, quote or date The object model records this entry’s own type as document.
  2. a register not met retrieved and hashed daily; the tier promises no person-verification The record tier this entry declares is core and its freeze reason is not recorded.
  3. unstated by the publisher not met a surface was read and it states no status term this publisher’s family declares; bounded to the surfaces read This entry carries no status basis and no recorded tool reading that found none, and no status read on file for it reports a surface that states none.
  4. verified by a person not met a person checked this entry against the primary source on a recorded day This entry records the check as made by tooling: checked_by reads machine.
  5. source access limited not met the publisher’s licence or its access policy limits what this record takes from the source The freeze reason this entry declares is not recorded, its licence class is open, and its record of whether the publisher excludes automated clients reads false.
  6. publisher metadata not met what is held is metadata the publisher publishes about the document — a catalogue entry or a stage record — not the document The resolution strategy this entry declares is direct_document, what its address points at is declared as document, and no stage the publisher publishes is held for it.
  7. observed not met the document at the address the publisher answered is retrieved and hashed here on a dated series No dated retrieval of the document this entry names carries a digest here.
  8. not currently retrievable carried no retrieval of the document this entry names has produced a digest No retrieval of the document this entry names has produced a digest here.

◆ carried — the entry meets this test and no state before it in the order does, so this is the state its evidence axis publishes · × not met — the entry does not meet this test, and the line beside it names what was read

Coverage contract#

Each term states what this record does for this entry and what it does not, derived from the entry’s own fields and its own series. It is a record of coverage, not a finding about the document.

Observed cadence how often this record has reached this entry’s address
Every interval between consecutive days holding an observation is 1 day. The term this record declares for the entry is “monthly”.
Text: public, and retained whether the publisher’s text is public, and whether prose from it is kept here
The publisher’s text is freely reproducible. Prose is retained from the retrieved bytes, so a quotation can be checked against it.
Hash what is digested for this entry, and of what
0 of 1 record(s) classified as being of the document this entry names carry a digest of the retrieved bytes; the entry’s whole series holds 135 record(s), and the rest are classified as records of something other than that document.
Status verification which check this record undertakes for the published status, and which it holds
This entry’s label undertakes to close an open status question by rule on a clock, with its reason, and to re-read a ratification on record against its observation every night. A machine read is recorded, dated 2026-09-07, and no person’s confirmation is.
Lifecycle tracked which lifecycle facts this record follows for this entry
This record follows no lifecycle fact for this entry: no effective date, no dated event, no archived version, no publisher stage record and no detected revision is held. That is what has been recorded here, not a reading of what exists. 36 of 132 tracked entries carry at least one such fact.
Known limits the limits this entry’s own record declares
None of the 8 limits this record can record is set on this entry. That is an absence of declared limits, and not a finding that the entry has none.

Why this entry is tracked#

The test an entry is admitted under is published in full, with its negative limb and its worked examples, at the inclusion rule. What this record holds about THIS entry's admission is below, each line naming the store it was read from.

Inclusion-rule limb which of the four limbs was applied
— No field in this record names which limb an entry satisfies, so none is stated for this one. Membership was closed as a human judgment on 2026-08-11, and the four-limb test is applied by a person rather than by code. This entry’s own stated subject is not read as a limb: a title word standing in for a rule would be a classification this record authored.
Admission entry the dated act that added this entry
— No admission entry is recorded for this entry. 21 of 132 tracked entries carry one, so an absence here is ordinary rather than a gap peculiar to this entry.
Declared tier-1 list a recorded judgement that this belongs
This entry is not a member of the declared tier-1 list. That list names 37 identifiers, of which 35 resolve to one of the 132 tracked entries, so most of the corpus sits outside it and non-membership says nothing about this entry on its own.
Admissions boundary the jurisdictions this record adds from
This entry’s jurisdiction is US. It is inside the admissions boundary ruled on 2026-08-16, which names 4 jurisdictions — EU · US · UK · International — and which is one of the two admission tests this record enforces in code. The other is that a candidate carry the publisher’s own address: a mention is not a citation.

Observation history#

Observed on 135 occasion(s) since 2026-08-08. 134 produced a content hash. No observation is marked ! (digest differed).

························································································································×··············

All 135 marks, one per observation, oldest first. · unchanged · ! digest differed · ~ fetched but rendered client-side, no hash · × could not be fetched, no hash · / withheld by the publisher’s terms — no fetch made.

Every one of the 87 days from 2026-08-08 to 2026-11-02 holds an observation.

Each mark links to the single observation it stands for, at that observation’s own address. The whole series, with every address, is at /observations/fda-device-cybersecurity. Any two of its retained observations can be set side by side at /compare/fda-device-cybersecurity. The same evidence as a packet, with its refusals and its integrity reference, is at /packet/fda-device-cybersecurity.

Every observation in this series is published, untruncated, at /api/v1/observations.json.

Of the retrievals classified as this document: same digest: not stated — no retrieval of this document carries a digest.

First observed
2026-08-08
Last observed
2026-11-02 (HTTP 200)
Fetch method
direct
Current hash
b52b706d5cca10eb0012d3205f0b49473176a2d3da7dd45cf8d268cfaa66648e
How this series is recorded
Recorded
observations: 135 · carrying a digest: 134 · marked ! (digest differed): 0 · first observed: 2026-08-08
Method
resolution: direct document · watch cadence: monthly · last fetch method: direct
Evidence
The most recent record is addressed at 2026-11-02·1.
Published at
/observations/fda-device-cybersecurity — every record of this row, with its address. /api/v1/series.jsonl — the same records for every row, one line each. Each observation is addressed by this row’s identifier, the date it was observed, and its sequence within that date — the same key /api/v1/series.jsonl publishes as `sequence`, counted in the order the store recorded them.
SHA-256: b52b706d5cca10eb0012d3205f0b49473176a2d3da7dd45cf8d268cfaa66648e This digest is a leaf of the integrity root, and the command that recomputes it is published at /verify/.

Clauses, definitions and sentences (as printed)#

Each string below is the string served for this entry at /api/v1/clause-anchors.json, /api/v1/definitions.json and /api/v1/modal-sentences.json, one block per observed text, each named by the first 12 characters of its content_hash as the JSON serves it: each clause anchor's id beside its label as the text prints it, each definition's term with its text where the derivation quotes it, and each sentence printing a listed verb that sits under the quote cap. A sentence or definition text over the cap is not cut: it is cited by the clause anchor it sits under, or by the stored reason no anchor is placed, its text withheld, and the count withheld is printed beside the count read. The block of the current text, where one is marked, is the one shown open.

Text b52b706d5cca (current text), first observed 2026-08-08

Clause anchors: no numbering read; 0 placed and 0 withheld.

Definitions: 0 read in this text, 0 with the text quoted and 0 with the text withheld.

Sentences printing a listed verb: 1 read in this text, 0 quoted and 1 withheld.

  • (no numbering read) 1 withheld: over the quote cap
Text d34d8c706d88, first observed 2026-09-07

Clause anchors: read; 6 placed and 0 withheld.

  • 1 1.
  • 2 2.
  • 3 3.
  • 4 4.
  • 5 5.
  • 6 6.

Definitions: served for the current text of an entry only.

Sentences printing a listed verb: 259 read in this text, 18 quoted and 241 withheld.

  • 6 Likewise, a device with a smaller software risk may have a significant cybersecurity risk.
  • 6 A device should be designed to eliminate or mitigate known vulnerabilities.
  • 6 Such plans must be maintained and updated as design and development progresses (Subclause 7.3.2).
  • 6 Documenting these views in premarket submissions should include both diagrams and explanatory text.
  • 6 Such traceability should exist throughout the cybersecurity risk management documentation.
  • 6 This may change the device’s functionality.
  • 6 This view should include the information recommended in Appendix 2.
  • 6 Each view should include detailed information as recommended in Appendix 2.
  • 6 Such verification shall confirm that the design output meets the design input requirements.
  • 6 For any third-party test reports, manufacturers should provide the original third-party report.
  • 6 Manufacturers should provide or make available SBOM information to users on a continuous basis.
  • 6 This should include notification to the user and logging of relevant information.
  • 6 Additional recommendations on coordinated vulnerability disclosure plans may be found in FDA’sPostmarket Cybersecurity Guidance.
  • 6 Generally, software should be regularly updated to maintain the supportability of the software.
  • 6 Downgrades can allow attackers to exploit prior, less protected versions and should be avoided.
  • 6 The version numbers intended to be installed should themselves be signed or have MACs.
  • 6 Despite best efforts, undiscovered, exploitable vulnerabilities may exist in devices after they are marketed.
  • 6 This should include detailed diagrams and traces for all communication paths as described below.
  • (no clause anchor before this sentence) 3 withheld: over the quote cap
  • 1 1 withheld: over the quote cap
  • 6 237 withheld: over the quote cap

Source health#

Counts and dates over a stated window. No figure here is a mark out of a hundred, no cell is ordered against another, and none of it is a statement about the publisher: a day this record did not reach is a fact about this record’s reach.

Fetch outcomes how the requests in the window answered
134 of 135 fetch records in the 90 calendar days ending carry no error. The 1 that carry one are recorded under blocked ×1.
Last fetched the most recent record in the whole series
— the latest day this record holds (). The method recorded is direct. What that record returned is in Observation history above.
Address stability where the requests actually landed
134 record(s) in the window recorded the address that answered, across 6 distinct address(es). 1 further record(s) carry no answered address and say nothing either way. 132 of them record that the request was redirected before it answered. The most recent answered address is not the one this entry declares. A request records where it landed and not only where it aimed.
  • https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket 118 record(s), 2026-08-08 to 2026-11-02
  • https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket?trk=public_post_comment-text 10 record(s), 2026-08-10 to 2026-09-26
  • https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket?utm_medium=email&utm_source=govdelivery 1 record(s), 2026-08-21 to 2026-08-21
  • https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket?ref=hackernoon.com 1 record(s), 2026-08-24 to 2026-08-24
  • https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket?utm_campaign=FDA%20Releases%20Draft%20Recom%20on%20Premrkt%20Sub%20Manag%20Cybersecurity&utm_medium=email&utm_source=Eloqua 2 record(s), 2026-09-02 to 2026-09-03
  • https://www.fda.gov/media/119933/download 2 record(s), 2026-09-07 to 2026-09-07
Access posture what the publisher declares, and what the requests met
Declared: no AI-specific disallow · crawlable yes · renders server-side. Met: 1 of 135 record(s) in the window were recorded as refused. A refusal is what one request of this record met on one day; it is not a policy the publisher stated.
Expected and observed cadence the declared term, the days held, and the days holding none
The term this record declares for this entry is monthly. Over its own window, to , 87 of 87 calendar days hold at least one observation. None holds none. Every interval between consecutive days holding one is 1, counted in days. Both figures are stated and the difference between them is not adjudicated here.
Days by outcome each day of the document's window, by what the store holds for it
15 calendar days expected, 2026-10-19 to 2026-11-02 · 15 observed (0 digest-bearing, 15 retrieval failed) · 0 withheld · 0 no request recorded. On 14 of the retrieval-failed days the request was answered from an address this record has not declared as the document’s, and that answer was hashed.
  • calendar days expected — one for each calendar day from the first observation classed as the document to the last day the store holds, because the collection is scheduled once a night; not the entry’s declared watch cadence
  • observed — a request for the document is recorded that day, and its record does not state that it was withheld or never left this machine
  • digest-bearing — a digest of the document is recorded that day
  • checked, unchanged (publisher-validator) — observed, and no digest of the document is recorded that day: the request carried an earlier reading’s validator and the server answered 304 “not modified”, which the record keeps as its outcome and basis; stated on a row only where the row has such a day
  • retrieval failed — observed, and no digest of the document is recorded that day
  • withheld — the day’s requests for the document are recorded as withheld, because the host’s filed terms withhold collection; none was sent
  • not sent, name unresolved here — the day’s requests for the document are recorded as never leaving this machine, because the host’s name did not resolve on it; attributable to this record, not to the host; stated on a row only where the row has such a day
  • no request recorded — no request for the document is recorded that day. This states what the store holds, not that no request was sent: the corrections page names the cause of each run of such days, including runs on which requests were sent and their records were not written

API and citation#

Cite this entry

Each format carries the permalink and the date this entry was observed. The observation date is part of the citation: the underlying source may have changed since.

Plain text

GxPlex. Cybersecurity in Medical Devices — Quality System Considerations and Content of Premarket Submissions [entry record]. Observed 2 November 2026. https://gxplex.com/r/fda-device-cybersecurity Primary source: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-system-considerations-and-content-premarket-submissions

BibTeX

@misc{gxplexrfdadevicecybersecurity,
  author       = {{GxPlex}},
  title        = {{Cybersecurity in Medical Devices — Quality System Considerations and Content of Premarket Submissions}},
  year         = {2026},
  note         = {entry record, observed 2 November 2026},
  howpublished = {\url{https://gxplex.com/r/fda-device-cybersecurity}},
  urldate      = {2026-11-02},
  url          = {https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-system-considerations-and-content-premarket-submissions}
}

APA

GxPlex. (2026). Cybersecurity in Medical Devices — Quality System Considerations and Content of Premarket Submissions [entry record]. Retrieved 2 November 2026, from https://gxplex.com/r/fda-device-cybersecurity

JSON

{
  "@context": "https://schema.org",
  "@type": "Dataset",
  "name": "Cybersecurity in Medical Devices — Quality System Considerations and Content of Premarket Submissions",
  "publisher": "GxPlex",
  "url": "https://gxplex.com/r/fda-device-cybersecurity",
  "temporalCoverage": "2026-11-02",
  "observation": {
    "url": "https://gxplex.com/observations/fda-device-cybersecurity#obs-2026-11-02-1",
    "observedDate": "2026-11-02",
    "sha256": "b52b706d5cca10eb0012d3205f0b49473176a2d3da7dd45cf8d268cfaa66648e",
    "verifiedAt": "https://gxplex.com/verify"
  },
  "isBasedOn": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-system-considerations-and-content-premarket-submissions"
}

observation.url addresses the single observation this citation rests on.

Every observation of this document is addressed and separately citable at the observation series.

Rights envelope — how this record handles the text of each entry listed
Entrytext_retainedlicence_classquote_allowedsnapshot_available
FDA device cybersecuritytrueopentruetrue

One row, for the entry this page records.

Each value is read by the same function the API reads, and each field is defined in the published schema. None of the four is a grant.

Sources#

Listed primary first, then the further addresses this record holds for this entry, then the route it was found by, then dated third-party copies. Repeated URLs appear once, at their first position.