Skip to main content
Print

EFTA01225932: C•CURE 9000 Hardware Configuration Manual and Evidence Limits

Snapshot

Field Details
Document EFTA01225932, pages stamped EFTA01225932 to EFTA01226471
Title C•CURE 9000, Version 2.50: Hardware Configuration Guide (document UM-130, revision R0)
Publisher Software House, a Tyco Security Products brand
Publication date December 2015 (the manual’s release date, not a date of purchase, installation or collection)
Length 540 pages by Bates range
What it is A generic manufacturer manual for configuring access-control hardware such as controllers, card readers, doors and elevators
Key limit The manual does not mention Epstein or any of his properties and does not show that this system was installed anywhere he lived

Introduction

EFTA01225932 is a 540-page manufacturer’s manual released with the Epstein files. It reproduces Software House’s C•CURE 9000, Version 2.50: Hardware Configuration Guide, published by Tyco Security Products in December 2015. C•CURE 9000 is commercial software that controls electronic door access, such as which key cards or fingerprints open which doors.

The manual matters because a contractor did propose C•CURE equipment for Epstein’s New York townhouse in 2013, in a quotation also found in the files (EFTA01088032). But the manual itself is generic. It explains how the product works for any customer and contains nothing about Epstein’s homes, guests or security settings. This guide explains what the manual covers and how to read it without over-reading it.


Key Takeaways

  • The record is a manufacturer’s guide to setting up commercial access-control hardware.
  • Its December 2015 date is when the manual was published, not when anything was bought or installed.
  • Screenshots and sample values in the manual are teaching examples, not settings from a real property.
  • No invoice, installation contract or covering email is attached to this file.
  • The machine-readable text that was searched contains no mention of Epstein, his properties or Ghislaine Maxwell.

Document Identity

The cover gives the product, version and title and carries the Software House and Tyco Security Products branding. The front matter gives the document number UM-130, revision R0, the December 2015 release date and a 2015 Tyco Security Products copyright notice. The Bates stamps (the numbers added to each page when documents are produced) run from EFTA01225932 through EFTA01226471. They identify this released copy but do not explain who originally held it or how it was collected.


What the Manual Covers

The manual describes how to set up the hardware side of an access-control system: networked controllers, card and fingerprint readers, floors, doors and elevators. It covers configuration screens, device groups, maintenance mode, communications, status fields and event handling. It is not a visitor log, a list of people allowed into a building, a set of camera recordings or a site survey.

Names such as iSTAR, apC and IP-ACM refer to product lines and components. A manual describing what a product can do is not evidence that any particular customer bought, switched on or used that feature.


Chapter and Page Index

The ranges below follow the manual’s table of contents. PDF page numbers match the manual’s numbered pages, so the Bates stamp on any page equals EFTA01225931 plus the PDF page number.

  1. The Hardware Pane: pages 19 to 56
  2. Maintenance Mode: pages 57 to 66
  3. Configuring Dialup: pages 67 to 78
  4. Configuring C•CURE iSTAR Clusters: pages 79 to 116
  5. Configuring C•CURE iSTAR Controllers: pages 117 to 276
  6. Configuring the IP-ACM: pages 277 to 294
  7. Configuring Advanced Processing Controllers (apC): pages 295 to 380
  8. Configuring RM Reader LCD Messages: pages 381 to 394
  9. Floors: pages 395 to 402
  10. Doors: pages 403 to 456
  11. Configuring Advanced Door Monitoring: pages 457 to 498
  12. Configuring Elevators: pages 499 to 530

Front matter and the table of contents take up pages 1 to 18, and the alphabetical index runs from page 531 to page 540.


How to Read the Screenshots

Configuration screenshots and example values show the vendor’s interface. An example controller name, network address, reader field or diagram must not be attributed to an Epstein property without separate evidence. Field-definition tables explain what each setting means; they are not an inventory of a real customer’s devices. Pages that discuss options such as encryption describe what the product offers, not what any site chose.


Evidence Appearances

Record or ID Date What It Shows Source
EFTA01225932 December 2015 (publication) Generic C•CURE 9000 version 2.50 hardware configuration manual epstein-data.com
EFTA01088032 October 28, 2013 Separate contractor quotation for the New York townhouse that names a C•CURE 9000 site server; a proposal, not proof of installation epstein-data.com

What the Record Does and Does Not Establish

  • It does not establish installation at Little St. James, the New York townhouse, Palm Beach, Zorro Ranch or any other property.
  • It does not establish a purchase, payment, installer, start-up date, equipment list or service relationship.
  • It does not identify any actual cardholders, access permissions or door events at an Epstein property.
  • It does not establish surveillance, recording, blackmail or misconduct by the manufacturer, an installer or a user.
  • Because it was published in 2015, it cannot show what version or settings were proposed in the 2013 townhouse quotation.

Records That Would Show an Installation

A claim that this system was installed at a specific property would need records such as an invoice naming the site, an installation agreement, an equipment schedule, a dated service report, a configuration export with reliable provenance, or correspondence naming the product and the location. Each would need its own assessment. Generic technical language should not be used to fill that gap.


Privacy and Copyright

The manual is vendor documentation, not a file of personal records. This guide does not reproduce credentials, personal details or settings for any real site. The manual keeps its publisher’s copyright notice, and release by the government does not by itself place a privately written manual in the public domain, so this page summarizes it rather than reproducing its instructions.


Conclusion

EFTA01225932 explains a commercial product, not the security arrangements at any identified property. Its value is as background for the separate, property-specific 2013 proposal. Any claim that the system was installed or used needs separate, reliably sourced records.


Questions and Answers

Does the December 2015 date show when equipment was installed?

No. It is the date the manual was published.

Are the screenshots real settings from Epstein’s homes?

No. They illustrate the vendor’s interface and explain what each field means.

Was C•CURE ever proposed for an Epstein property?

Yes. A separate October 2013 contractor quotation (EFTA01088032) proposed a C•CURE 9000 site server for the New York townhouse. No record reviewed shows that it was installed.

What would connect the product to a particular property?

A site-specific invoice, installation agreement, equipment schedule, service report or reliable configuration record.


Source Document

Open EFTA01225932: C•CURE 9000 Hardware Configuration Guide (540 pages). The file is about 24 MB and may take time to load.


Sources

  1. EFTA01225932, C•CURE 9000 Hardware Configuration Guide; official copy at the Department of Justice, Data Set 9.
  2. EFTA01088032, Sawyers biometric entry proposal, October 28, 2013.
  3. EpsteinWiki: Inside Jeffrey Epstein’s Surveillance Infrastructure.
Previous EFTA01221503: UVI RTPark Tax-Incentive Rules and Thomas World Air Records
Next EFTA01256987: Source Guide to Epstein’s December 2018 Database Report
Table of Contents