Florida Courts Technology Standards
Section VI
Integration and Interoperability
6.0.0 | CHAPTER 6 INTRO
6.1.0 | BACKGROUND
6.2.0 | REQUIREMENTS AND STANDARDS FOR INTEGRATION & INTEROPERABILITY
6.2.1 | DIAGRAMS
Figure 1. Florida Court System Network Topology Overview
Network Topology Overview
Figure 2. Circuit Court Approved Clerk Interface
Approved Clerk Interface
6.3.0 | INTEGRATION REQUIREMENTS AND STANDARDS
6.3.1 | INFRASTRUCTURE STANDARDS AND REQUIREMENTS
The goal of these guidelines is twofold: first, provide a blueprint for a robust extensible infrastructure that will support the growth, integration, and interoperability of information systems supporting the judicial branch; and secondly, reduce aggregate costs through standards that offer economies of scale.
6.3.1.1 Desktop PC Standards
• Judge Chambers. Video display: 24” or greater with capability for dual displays.
• Video Display. Video display replacement lifecycles may differ from desktop lifecycles based on functionality and usage requirements. Touch screen displays shall be used where deemed appropriate by the court.
| Details | ||
|---|---|---|
| Hardware | Processor | Quad Core Business Class Intel or AMD (3.4 GHz or greater) |
| Memory (RAM) | 8 GB or greater | |
| Storage | 500 GB Solid State Drive (“SSD”) | |
| Video | DirectX 12 or greater Capable (WDDM Driver Support recommended) | |
| Graphics RAM | 256 MB or greater, the system should be able to accommodate dual displays | |
| Sound | Audio is required in accordance with the planned use of the system | |
| Ports | HDMI and multiple USB 3.0/USB C ports as required | |
| Lifecycle | 3 years | |
| Network Connectivity | Bandwidth | 100/1000BaseT Ethernet, wireless as required |
6.3.1.2 Laptop Standards
Figure 4. Recommended Laptop Configurations
| Details | ||
|---|---|---|
| Hardware | Processor | Quad Core Business Class Intel or AMD (3 GHz or greater) |
| Memory (RAM) | 8 GB or greater | |
| Storage | 250 GB Solid State Drive (“SSD”) | |
| Graphics | DirectX 12 or greater Capable (WDDM Driver Support recommended) 256 MB (in addition to RAM) | |
| Sound | Audio required | |
| Ports | HDMI or mini-display USB 3.0/USB C ports as required | |
| Lifecycle | 3 years | |
| Bandwidth | Integrated 100/1000 Ethernet LAN (standard) | |
| Network Connectivity | Wireless | Internal adapter supporting 802.11 b/g/n/ac |
6.3.1.3 Client (Desktop/Laptop) Software Standards
Figure 5. Software Requirements and Standards
| Software | Details |
|---|---|
| Operating System | Windows 10 Professional or higher (OS must be active in the MS Support Lifecycle for patches and updates) |
| Office Suite | G Suite, Office365, or Microsoft Office version currently supported by Microsoft |
| Other Productivity Software | 1) PDF Reader 2) PDF Writer |
| Security Software | 1) Anti-virus 2) Anti-malware |
6.3.1.4 Mobile Devices
6.3.1.5 Recommended Mobile Device Configurations
6.3.1.6 Mobile Device Computing: Any device, anytime, anywhere
Mobile devices generally refer to smartphones and tablet devices that support multiple wireless network connectivity options (primarily cellular and Wi-Fi), as well as voice and data applications. This section will focus on the mobile computing or data element.
MDM products have been developed to mitigate threats to mobile devices by enabling enterprise-controlled device configuration, security policy enforcement, compliance monitoring, and response (e.g., remotely lock and/or wipe a mobile device that has been reported as lost or stolen). MDM solutions typically include an enterprise server(s) component and an application installed on the mobile device to manage device configuration and security and report device status to the MDM.
Small Florida court technology budgets juxtaposed against the tremendous popularity of the smartphone and tablet have led to an unprecedented rise in Bring Your Own Device, or BYOD. Standards to exercise control, manage expectations, and define acceptable use policies should be developed and implemented for all such users.
• DDNA. Securing mobile devices should focus on the following 4 categories:
2. Data security: protecting data at rest even on a lost/stolen device, such as an MDM.
3. Network security: network protocols and encryption of data in transmission.
4. Application security: security of the applications, and operating system, such as a MAM.
2. Allow remote location of devices.
3. Allow remote wiping of device’s drive/data.
4. Allow remote locking.
5. Detect rooted/jailbroken phones, which are more vulnerable to malicious code.
6. Inventory of devices.
7. Policy compliance.
To mitigate the threat of malicious or vulnerable mobile applications to mobile devices, the court should use MAM to provision for application whitelisting or allowing installation of mobile applications from authorized enterprise application stores application blacklisting, which blocks the installation of known vulnerable applications.
• Recommended MAM Requirements
2. Control the push/pull of updates to devices.
3. Allow for the remote installation of applications.
4. Allow for the remote wiping of non–standard applications.
5. Whitelisting of select applications from public sites.
6. Blacklisting of select applications based either on application or site.
7. Application inventory.
2. For BYOD devices:
b. What is the extent of policy enforcement versus device support?
d. What enforcement exists for connectivity to unsecured networks (e.g., public wireless connection)?
e. Is confidential data storage on the device prohibited?
b. What is the data backup policy?
c. Are secure network connections enforced?
d. What is the acceptable use of data storage on the private or public cloud?
For internal wireless court/county networks, VLANS or MAC address filtering provide additional controls over secure connectivity.
Bluetooth settings, when not in use, should be turned off.
• Best Practices for Non-CJIS Connections. For wireless connections, only use properly encrypted connections. There are other potential confidential or sensitive data transmitted outside of CJIS systems.
Be aware of Federal Information Processing Standards (“FIPS”) 71A-1 Subsections 001-023, and the U.S. Department of Justice, Federal Bureau of Investigation, Criminal Justice Information Services Security Policy Sections 4.3, Personally Identifiable Information, and Section 5 regarding securing technology that accesses, stores, transmits and logs Criminal Justice Information governed by this referenced policy. The most current version of this policy can be viewed at http://www.fbi.gov/about-us/cjis/cjis-securitypolicy-resource-center/.
6.3.1.7 Servers
6.3.1.8 Network Components
• Courts Local Area Network (“LAN”) Considerations/Recommendations
A standard for agency LAN implementations should be established. It is recommended that the standard include the following:2. Ethernet topology (over unshielded twisted pair cabling).
3. High-speed copper (UTP) to the desktop (CAT 5e or better).
b. Switches should have fiber uplink capability.
c. Switches shall be manageable via IP or other remote protocol.
7. Bandwidth standards and requirements within and among each judicial location are recommended at:
b. Gigabit to workstations
Any LAN technology dedicated for use by the court should meet the following requirements:
| Feature Sets | IP Routing, VRRP, HSRP, STP enhancements, 802.1s/w, IGMP snooping, IEEE 802.3af Power over Ethernet (PoE). |
| Security | ACL, port security, MAC address notify, AAA, RADIUS/TACAC+, 802.1x, SSH, SNMPv3, IPv6 |
| Advanced QoS | Layer 2–4 QoS with Class of Service (CoS)/Differentiated Services Code Point (DSCP), & Differentiated Services Model (DiffServ) supporting shaped round robin, strict priority queuing. QoS compliant with DiffServ (IETF) standards as defined in RFC 2474, RFC 2475, RFC 2597 and RFC 2598 and DSCP (IETF) standards as defined in RFC 791, 2597 2598, 2474, 3140 4594[MediaNet]. 802.1p, 802.1Q, 802.11e Resource Reservation protocol (RSVP) in RFC 2205. |
| Management | One IP address and configuration file for the entire stack. Embedded web-based cluster management suite to Layer 2/3/4 services easy configuration of network-wide intelligent services in local or remote locations automatic stack configuration. |
| Performance | Distributed Layer 2 and Layer 3 distributed providing wire-speed switching and routing via Gigabit Ethernet and Fast Ethernet configurations |
| Deployment | Automatic configuration of new units when connected to a stack of switches. Automatic OS version check of new units with the ability to load images from a master location. Auto-MDIX and Web setup for ease of initial deployment. Dynamic trunk configuration across all switch ports. Link Aggregation Control Protocol (LACP) allows the creation of Ethernet channeling with devices that conform to IEEE 802.3ad. IEEE 802.3z-compliant 1000BASE-SX, 1000BASE-LX/LH, 1000BASE-ZX, 1000BASE-T and CWDM physical interface support through a field-replaceable small form-factor pluggable (SFP) unit. 10 gigabit Ethernet IEEE 802.3-2008 |
| Configuration/ Survivability | Switches must work standalone and in a stacked configuration. Stack up to 9 units, Separate stacking port. Minimum 32Gbps fault-tolerant bidirectional stack interconnection. Master/slave architecture with 1:N master failover. Less than 1 second Layer 2 failover with nonstop forwarding. Less than 3 second Layer 3 failover with no interrupt forwarding. Cross-stack technology, cross-stack QoS Single network instance (IP, SNMP, CLI, STP, VLAN). Minimum of 24 Ethernet 10/100/1000 ports and 2 SFP uplinks with IEEE 802.3af and pre-standard Power over Ethernet (PoE). |
| Software | Intelligent services: Layer 3 routing support via RIP, OSPF, static IP routing. Dynamic IP unicast routing, smart multicast routing, routed access control lists (ACLs), Hot Standby Router Protocol (HSRP) support, and Virtual Router Redundancy Protocol (VRRP). |
• WAN Considerations/Recommendations
2. The current infrastructure supports high-speed switching technology The WAN infrastructure should include the use of TCP/IP for interagency communications.
3. Where possible, the communications infrastructure should provide for coexistence with existing architectures until these architectures are compliant with the standard.
4. Multi-protocol WAN bandwidth may have to expand to handle traffic while supporting other emerging applications and business requirements.
5. Each courthouse or remote facility should have a high-speed connection back to the State network unless a high-speed network has already been provided by the county. Network speeds for each circuit will vary depending on bandwidth requirements.
6. Throughput on the WAN should be benchmarked at key junctures before the system becomes operational It should be monitored continually thereafter.
7. State-provided bandwidth is a shared resource; accordingly, bandwidth management at the circuit level is strongly recommended.
6.3.1.9 Wireless Technologies
• General Wireless Guidelines
2. Change the default level of product security – out of the box, WLANs implement no security.
3. Change the out-of-the-box settings – do not use default or null SSIDs or passwords.
4. Implement wireless access points on switched network ports.
5. Develop and publish standards and policies for departmental WLANs.
6. At a minimum, use 256-bit keys or greater.
7. Implement MAC address tracking to control network security.
8. Monitor access logs or use network-based instruction detection to detect unauthorized access or attack.
9. Highly sensitive networks should use a minimum of 256-bit encryption. The SSID should not be broadcast, and MAC authentication should be required.
10. Disable Wi-Fi Protected Setup (“WPS”).
11. Each circuit should develop a practical and comprehensive wireless solution including a detailed IEEE 802.1x-based security plan.
The following general guidelines should be considered when developing and implementing a wireless security plan for your WLAN.
Multi-Point Wireless Guidelines
2. Perform site surveys in advance of access point placement to ensure adequate signal coverage and identify related power requirements.
3. Implement wireless access points on switched network ports.
4. Address security on two levels: encryption and authentication.
5. The newest security standard is 802.11-2007 (sometimes referred to as WPA2), incorporating authentication by 802.1x standard. 802.1x supports authentication server or database service including Remote Authentication Dial-In User Service (RADIUS), LDAP, and Windows domain, and Active Directory. Encryption in 802.11-2007 is strong AES.
6. Change the “out-of-the-box” settings – do not use default or null SSIDs or passwords. At a minimum, activate the default level of product security.
7. Set access point SSID broadcasting to “OFF”.
8. Consider implementing VPN with strong encryption for wireless networks. Place access points outside of the firewall. Use VPN for connectivity to the intranet.
9. Implement MAC address authentication and tracking to control network security. Utilize monitoring software to limit network access based on the user’s physical location and IP address, granting or denying access to services as needed.
10. Implement additional authentication if supported by the vendor (RADIUS, LDAP, etc.).
11. Monitor access logs or use network-based intrusion detection to detect unauthorized access or attacks.
12. All publicly accessible Wi-Fi must be outside the court’s internal network.
Point-to-Point Wireless Guidelines
2. Distance/Path: Line of sight is required.
3. Tower Locations and Access.
4. Security
b. Network security.
6. Management: Utilities should be Simple Network Management Protocol (“SNMP”) compliant.
7. Warranty and Maintenance: Equipment, tower climbing, and maintenance should be included.
8. Each circuit should develop a practical and comprehensive wireless solution including a detailed IEEE 802.1x-based security plan.
6.3.1.10 Security Standards
Information Security Standards are organized into four categories:
• Personnel Control
• Network Control
• Physical Security
• Device Control
1. Access Rights and Privileges: Computer-resident sensitive information shall be protected from unauthorized use, modification, or deletion by the implementation of access control rights and privileges.2. Anti-Virus Protection: Platforms that are susceptible to malicious code shall be equipped with adequate software protection when such protection is available.
3. Authentication of Desktop Users: Desktop access shall be secured and authenticated using adequate security techniques.
4. Backup Policy: Data storage devices shall undergo sufficient periodic backup to protect against loss of information.
5. Business Continuity & Disaster Recovery: Formal business continuity and disaster recovery plan(s) shall be documented and implemented per applicable Florida State Courts policy and administrative rules.
6. Transmission of Sensitive Data: Sensitive data (security management information, transaction data, passwords, and cryptographic keys) shall be exchanged over trusted paths, using adequate encryption between users, between users and systems, or between systems.
7. E-mail Anti-Virus Protection: Proactive installation and management of software/hardware to safeguard against the injection of malware, viruses, or other code via e-mail or e-mail attachments is required.
8. Platform Level Administration (Local): Local access to system console functions shall be restricted to appropriately authorized personnel.
9. Platform Level Administration (Remote): Remote access shall be secured via adequate authentication and restricted to appropriately authorized personnel.
10. System Administration Privileges: System administration privileges shall be locally granted only to appropriately authorized personnel.
• Personnel Control
2. Acceptable Use Training: All employees shall undergo training, briefing, and orientation as deemed necessary by the circuit to support compliance with all elements of established acceptable use and applicable information security policies and guidelines.
3. Remote Access Policy: Where applicable, each circuit will maintain a written remote access policy.
4. Sensitive and Exempt Data Handling: All employees with access to sensitive or exempt data shall be trained to handle the data in compliance with relevant guidelines. The Florida Department of Law Enforcement (“FDLE”) establishes CJIS guidelines governing the access by any workstations to FCIC/NCIC data directly or through the Judicial Inquiry System (“JIS”).
5. Incident Response: Incident Response (“IR”) procedures shall be developed and maintained. IR procedures will guide appropriate steps to take in response to breaches in devices, networks, and physical security.
• Network Control
2. Device Resistance: All critical devices within the perimeter network shall be resistant to attack by known threats for which there are available defenses.
3. Network Audit Logs: Network audit logs shall provide sufficient data to support error correction, security breach recovery, and investigation. Network audit logs should be retained for a minimum of three months.
4. Remote Access: All remote access methods providing access to critical systems shall be identified and inventoried. Remote access to the court’s network and resources will only be permitted providing that authorized users are authenticated, data is encrypted across the network, and privileges are restricted. Remote access logs should be recorded for a minimum of three months. A centralized point of access is preferred.
5. Wireless Network Security and Management: All wireless networks and devices shall be locally authorized by each circuit and have adequate security configurations.
6.3.1.11 System Management Tools
• Network management applications that are deployed and integrated to support network management requirements, including hub, switch, and router management. SNMP compliant hardware; when in a Windows environment, Windows Management Instrumentation (“WMI”) compliance is required.
• Network management tools that have the ability to monitor across VLANs, WANs, and disparate network architectures, including wireless networks.
• Either IPv4 or IPv6 are protocols.
• The tools should contain the ability to monitor, report, and block offending IP addresses or infected network segments.
• Network Quality of Service (“QoS”) management utilities. Preference for SSH or SSL over telnet or HTML for network management tools.
• Traffic monitoring systems that utilize a learning mechanism establishing initial baselines that are time corrected and display anomalous traffic with reasonable swiftness. Rules-based equipment should allow for frequent base table updating.
• Desktop management tools deployed and integrated to support workstations, software distribution, desktop inventory control, and asset tracking of desktop configurations and installed software (“metering”). Ghost or equivalent imaging software, patch management (such as Windows Server Update Services (“WSUS”)), and detailed, flexible reporting mechanisms.
• Server management tools should be SNMP compliant, have the ability to monitor server health, including disk, memory, process utilization, and when possible, power consumption, and when possible, support Lightweight Directory Access Protocol (“LDAP”).
When evaluating system management tools administrators should consider the following criteria:
• “Agent-less” tools are not required but may be preferred.
• Robust reporting/metrics functionality is preferred and strongly recommended.
• E-mail/text alerts for virus monitoring should be available for all systems. Encryption should be required for some types of e-mail at rest and in route.
• Remote management of network, desktops, servers, provided software meets the established security standards is preferred. A health report should be periodically generated, and contain the following information when possible:
• Login reports for both successful and failed attempts (wireless, RADIUS, VPN, etc.).
• Switch/router/hub changelogs.
• Wireless connections.
• Server health (average CPU load, RAM and disk utilization, etc.).
• Active Directory additions/deletions/changes.
• Restricted traffic attempts and perceived network anomalies.
6.3.1.12 Audio and Video Teleconferencing
• Digital Audio and Video Conference Standards
2. Separate VLAN for video.
3. Standard definition speed: 384K.
4. High-definition speed: 768K
5. Duplex: Full (512 units = half).
6. Network speed: 100Mbps (502 units = 10Mbps).
7. Switch and codec: hard-coded speed/duplex.
8. Video communications must support the H.264 SIP multimedia standards.
9. Audio conferencing must support G.711 audio compression
10. Low Resolution: Based on communications availability. H.323 standard should use a minimum of 256Kbps bandwidth per concurrent video session.
11. QoS tag: DSCP AF41.
12. Ports: 1719, 1720, 3230-3253 TCP/UDP
6.3.1.13 Cloud Video Conferencing
6.3.1.14 Court Reporting Technologies
• Reference
6.3.1.15 Technical Support
On-call is required to support 24/7 operations.
6.3.1.16 User Support Ratio
Specialized technical services may require dedicated support staff depending on the environment. Specialized services may include:
• Security
• Audio Video
• ADA
• Communications
2. Voice
• Web
2. Intranet
• Database Administration
• Server Administration
Funding for on-going training must be included with staff to maintain the skill sets required to support the environment.
6.3.1.17 Courtroom Technology Standards
• Courtroom – Hearing Room Technology Minimum Requirements
For criminal proceedings, courtrooms and hearing rooms need to have the infrastructure in place to deliver information and services to the courtroom. Information is vital whether it is information on a computer screen, a juror’s ability to hear the witness, or the ability to set up evidence presentation tools. For Civil proceedings, equipment may be used if available; otherwise, attorneys are responsible for providing the equipment needed for evidence presentation.Posting a disclaimer on the circuit’s website concerning the provided technology is recommended. An example is listed below:
Courtroom technology is provided as a courtesy to the legal profession and court participants. While the court will make every effort to ensure the equipment is working properly, the court does not guarantee the reliability or availability of the equipment. It is presumed that anyone using courtroom technology is properly trained to do so. The court is not responsible to provide educational or technical support for these services. By using this technology, the user agrees to hold the court harmless for any equipment failure or corruption of data, for any court-related proceeding, and to not seek to delay/reschedule court proceedings due to same. Finally, users agree to be prepared to proceed without using technology should the circumstances warrant such action.
• Infrastructure
When building new courtrooms, plans shall include conduit and cable paths to support existing and future technology. Raised flooring is recommended for courtrooms to allow for easy access. Floor boxes can be used to support future expansion. If using floor boxes, industry-standard termination must be accommodated into the design of the floor boxes and wiring practices. See Figure 6 for a typical courtroom design.• Courtroom Technology Guidelines
2. ADA assisted listening devices.
3. Video display(s).
4. 1 pan/tilt/zoom camera (minimum).
5. DCR (when applicable).
6. LAN access for the judge and the clerk of court.
• Recommended Optional Integrated Equipment
2. Wireless presentation interface.
3. Sidebar microphones.
4. Gallery microphones.
5. Video displays/Intelligent displays (capable of supporting different multi-media sources).
6. Touch screen video displays (witness stand for evidence presentation).
7. 4 pan/tilt/zoom cameras (suggested camera options: judge, witness, courtroom, and evidence/jury. The evidence camera should be mounted in the ceiling at a location that allows evidence to be placed underneath for presentation.
8. Network access/Wi-Fi for participants.
9. Remote interpreting A/V equipment.
10. Video conferencing.
11. Teleconferencing.
12. Analog stereo audio, VGA, component, and HDMI inputs and/or wireless media display devices, display port, and other industry-standard connections.
13. Media plate
14. Remote technical support and control.
15. White noise cancellation for sidebar conferences.
16. Where needed, the microphones should be configured to work with the DCR.
• Hearing Rooms Guidelines
While sound systems may not be needed in all hearing room types, other equipment is essential. These rooms shall include the following:2. Video display(s).
3. 1 camera.
4. DCR (pre-wired if possible).
5. LAN access for judge and clerk
2. Wireless presentation interface.
3. Remote interpreting A/V equipment.
4. Video conferencing.
5. Teleconferencing.
6. Analog stereo audio, VGA, component, and HDMI inputs and/or wireless media display devices, display port, and other industry-standard connections. These inputs can be installed in a floor box or wall plate.
7. Remote technical support and control.
• Optional Mobile Technology
If funding is unavailable for integrated courtroom technology solutions, mobile systems are recommended. Evidence presentation systems should be able to display a wide range of types/formats/sizes of physical and digital evidence used in today’s courtrooms. An evidence presentation system should include (but not be limited to) the following support components:1. Display
Mobile display (TV/LCD screen) or projector:A projector should support multiple resolutions with sufficient brightness for viewing in ambient light (will vary based upon projected image size) + projector screen.
The system should provide audio/video outputs compatible with the courtroom’s integrated video displays/audio/DCR system (if applicable).
2. Cables
Audio/video presentation systems should support prevailing audio/video transmission cable standards such as analog stereo audio, analog stereo audio, VGA, component, and HDMI.3. Physical Media
Audio/video presentation systems should support prevailing physical media standards such as CD (R/RW), DVD, (+R/RW), USB storage device (flash or HD), CompactFlash, SD/Smartmedia, Memory Stick, Blue-ray, and cell phone connectivity.4. Digital Audio/Video Standards
Audio/video presentation systems should support prevailing digital audio/video standards such as Audio CD, DVD, VCD, SVCD, WMV, QuickTime, Mpeg4, MP3, OGG.5. Overhead Projector
6. Document Camera
Figure 6. Courtroom Drawing
 | Press Plate Location. Contractor shall install a 8”x8”x3” Deep Junction Box flush in wall at 18” AFF. Install two 2” conduit from the plate to the Cable tray on the 1st level |
 | Floor Box/Pocket; Install an Ace Backstage 124SL Floor pocket or approved equal. The floor pocket shall be able to contain a minimum of 4 A/V gangs, 1 duplex receptacle, 2 RJ-45 connectors, and two spare single gang plates. Each pocket shall have two 2” conduits for future A/V cabling and one 1” conduit spare. These conduits shall be installed to the cable tray on the 1st level. A separate conduit shall be installed for the duplex receptacle and a separate conduit for the RJ-45 connections. Refer to the telecom and power plans for information on these systems. |
 | Ceiling Speaker Location; location is approximate and shall be coordinated with the A/V contractor prior to roughing in; a junction box shall be installed at each location. Install a ¾” conduit from the speaker to the other speakers on the same zone. The homerun conduit for each zone shall be installed to the cable tray on the 1st level. |
 | Ceiling Hanging Microphone Location; location is approximate and shall be coordinated with the A/V contractor prior to roughing in; a junction box shall be installed at each location. Install a ¾” conduit from the microphone to the cable tray on the 1st level. |
 | Button Microphone Location; location in casework is approximate and shall be coordinated with the A/V contractor prior to roughing in; a stub up ¾” conduit shall be installed in the casework. The conduit shall be routed to the cable tray on the 1st level. |
 | Sidebar Button Microphone Location; location in casework is approximate and shall be coordinated with the A/V contractor prior to roughing in; a stub up ¾” conduit shall be installed in the casework. The conduit shall be routed to the cable tray on the 1st level. |
 | A/V Plate Location; install a 12” wide x 6” tall x 3” deep junction box flush in casework. Junction box shall be located 18” above the bottom of the casework. Install two 2” conduits and one 1” conduit from the junction box to the cable tray on the 1st level. |
 | A/V Camera Location; install a junction box flush in the wall at each location. Install a ¾” conduit from the junction box to the cable tray on the 1st level mounting height shall be coordinated with the A/V contractor prior to install. |
 | A/V Camera Location; install a junction box flush in the wall at each location. Install a ¾” conduit from the junction box to the cable tray on the 1st level mounting height shall be coordinated with the A/V contractor prior to install. |
 | TV Location; install a junction box flush in the wall at each location. Install a ¾” conduit from the junction box to the cable tray on the 1st level mounting height shall be coordinated with the A/V contractor prior to install. |
 | TV Location; install a junction box flush in the wall at each location. Install a ¾” conduit from the junction box to the cable tray on the 1st level mounting height shall be coordinated with the A/V contractor prior to install. |
 | DCR Light Location; install a junction box flush in the wall 12” above the bottom. Install a ¾” conduit from the junction box to the cable tray on the 1st level. |
 | Hearing Impaired IR Location; install a junction box flush in the wall at a height to be determined by the A/V contractor. Install a 1” conduit to the cable tray. |
6.4.0 | REQUIREMENTS FOR INTEROPERABILITY & DATA EXCHANGE
The technical standards listed below have been developed across all industry sectors and have the joint backing of many software development companies (e.g., Microsoft, Oracle, Sybase, IBM) that have recognized that information exchange and the resulting gains in productivity and efficiency are critical strategic goals of improved system performance.
6.4.1 | SOFTWARE APPLICATIONS
b. Standards compliant Cascading Style Sheets 2.1 and later
b. Development processes such as Model-View-Controller (“MVC”).
c. The presentation layer should access information via a web service.
d. Where possible, code should be executed on the server (server-sidecode), not the client.
e. eXtensible Markup Language (“XML”).
f. Simple Object Access Protocol (“SOAP”)
g. Web Services and/or Representational State Transfer (“REST”) web services.
h. JSON (“JavaScript Object Notation”).
i. American National Standards Institute Structured Query Language (“ANSI SQL”).
j. W3C ADA/508 compliance.
k. Open Database Connectivity (“ODBC”), Java Database Connectivity (“JDBC”), OLEDB, Database Native Clients.
l. Remote Procedure Call (“RPS”)
b. The Data Exchange Standards, adopted in May 2016, but the FCTC provide a Data Security Model standard to which applications should adhere when applicable.
6.4.2 | DATA TRANSMISSION
6.4.3 | DATABASE STANDARDS
• Use ANSI SQL.
• Package appropriate database drivers with the database platform.
• Be secured using industry-proven algorithms, techniques, platform-supplied infrastructure, and vendor-tested and supported technologies.
• Be backed up per the Backup of Electronic Records standards in Section 8.5.
• Have a tested recovery plan.
6.4.4 | DATABASE CONNECTIVITY
The communication technologies (database drivers) needed to allow transmittal and sharing of access to and utilization of information for various databases in the circuits may include:
• Object Linking and Embedding (“OLE DB”).
• Java Database Connectivity (“JDBC”).
• Database Native Drivers.
Figure 7. Conceptual Data Exchange Environment
6.4.5 | ARCHIVAL STORAGE OF ELECTRONIC DOCUMENTS
The Florida Supreme Court approved PDF/A-2 as the document storage format for electronic court documents in June 2019. Section 8 outlines the current document storage and backup of electronic records requirements.
6.5.0 | CLOUD COMPUTING
6.5.1 | APPROVAL PROCESS
6.5.2 | RISKS
Because Service Level Agreements (“SLA’s”) can change often and with short notice, a plan must be in place to monitor and audit the impact that such changes to agreements could have and mitigate their impact.
6.5.3 | STORAGE RESTRICTIONS
2. Administrative Records
Data in classification 1 must reside within the United States. Data in classification 1 shall be encrypted, both in transit and at rest.
Data in classification 2 may be stored outside the United States, but the data must be stored in such a way as to facilitate copying of the data or a portion thereof in an amount of time similar to the amount of time such duplication would take if the data were stored within the United States.
6.5.4 | DATA ENCRYPTION
6.5.5 | BEST PRACTICES
• Any agreement should include a clause requiring law enforcement to work through the custodian of the record when requesting access to records rather than direct access.
6.5.6 | RESOURCES
• Security
o PCI Security Standards
o ISO/IEC 27001:2013
o ISO/IEC 27002:2013
o Compliance with Justice Partner standards for current & future integrations
You might need to reference it during your pursuit of justice.
For instance, you might need to examine this handbook in order to protect yourself from organizations/judges/lawyers who break the law (see this example of a Florida judge who outright committed perjury).
Nevertheless – and as always – please get the justice you deserve.
Sincerely,
www.TextBookDiscrimination.com
