Fla. Admin. Code Ann. R. 60FF-1.013 - State Intranet Users: Clearance Requests Related to Interoperability and Security

(1) Clearance Requests must be submitted by SUNCOM Customers that are:

(a) Using the State Intranet and;

(b) Are not Required Users and;

(c) Are intending to initiate Network Solutions that result in the purchase or lease of Network Services, Network Software or Network Equipment and these network resources:

1. Make use of the Internet Protocol and;

2. Are not provided through SUNCOM.

(2) These Customers must follow the submittal standards established in Rule 60FF-1.004, F.A.C., to provide the following as a part of the Clearance Request:

(a) Address, city, state, zip code where the primary part of the Network Solution shall take place;

(b) Date that the Network Solution is to be implemented;

(c) Any pending SUNCOM orders affected;

(d) Brief summary of Business Objectives;

(e) General descriptions of the Network Equipment, Software or Services comprising the Network Solution;

(f) If known at the time of submittal of the Clearance Request, the entity that is expected to provide the solution with contact information including: entity name, city, state, representative name, telephone number and electronic mail address;

(g) A "Customer Notice of Security Concern Regarding a Network Solution" in accordance with Rule 60FF-1.005, F.A.C., if the Network Solution creates any Security Exposures in violation of Rule 60FF-3.004, F.A.C.

(3) A statement must be included that the Customer shall commit to Rule 60FF-3.005, F.A.C., and be prepared to demonstrate this commitment by also making purchasing documents available to the Department.

(4) The Customer must provide any subsequent supplementary documentation requested by the Department that shall clarify or elaborate on the Network Solution and is needed to properly evaluate its potential impact on the State Intranet and its other Customers.

Notes

Fla. Admin. Code Ann. R. 60FF-1.013

Rulemaking Authority 282.702(2), (9), 282.707(2) FS. Law Implemented 282.702(2), (8), (12), 282.703, 282.704, 282.705, 282.706, 282.707 FS.

New 6-25-08.

New 6-25-08.