And it all takes time. Co-use agreements are usually coordinated between the item security office that sponsored the host SCIF and the security office of the benefit or client element. For example, if a company has an NGO-accredited SCIF but wants SCIF to support an NGA program, the NGA`s security office works with the NGO`s security office to ensure that all NGA rules regarding SCIF are followed. After a full review, including the vote on possible waivers, the NGA`s security office will approve the work of the NGA, which must be carried out within the NGO-accredited SCIF, in accordance with the terms of a final co-use agreement. You should target the host`s security offices and identify items as soon as program-specific security requirements can be identified. Depending on the existence and nature of waiver declarations, the process can be long and complex. Rapid and constant coordination will increase the likelihood of co-use of SCIF slightly, but significantly. In scif co-use, a sponsorship item that has previously accredited a SCIF (host) allows a non-sponsoring element (the “tenant” or “winner”) to use an SCIF for its own mission. Details are negotiated, agreed and recalled in a co-use agreement. Co-use of SCIF promotes efficiency and competition. It uses an existing IC asset to increase total emission capacity and increases the number of eligible competitors for a given program. It allows innovative small businesses to compete with work that would otherwise prevent them from hunting. Of course, small businesses are working to promote the use of SCIF.
Depending on the requirements of the mission, there are now exceptions both in cases where uniform safety requirements cannot be met and when they must be exceeded. See in general ICS 705-1 (H) (a) – (b). As a result, CSCs accredited today are very different in terms of compliance with “uniform” requirements; Some meet them, others surpass them, and others fall too short. As well as the Director of the National Intelligence Service (DNI). In 2010, the DNI adopted Community Intelligence Directive 705, which aimed to establish uniform physical and technical safety requirements (“uniform safety requirements”) for all GBS. The stated objective was to “promote the effective, consistent and reciprocal use of scifs in ICR.” ICD 705 (B) (1). The mandate should ensure that from that date, all CICs intended for mutual use by all elements of the ICR are established, operated and maintained. See ICD 705 (D) (7). But there was a catch. Despite the DNI`s best intentions, SCIFs – like costumes – are not “one-size fits all.” A little sewing is always needed.
As one friendly IC program manager said recently, “we have different requirements because of the work that has been done.” The original CDI therefore provided for a strict exception: in the case of indefinite “exceptional circumstances”, uniform safety requirements may be removed. In short, the diversity and complexity of the various IC programs have resulted in a multitude of exceptions. Soon, the exception would swallow the rule. The result is that IC program managers and industry security experts are constantly working to reconcile a tension: a political environment that, on the one hand, promotes the development and approval of a co-use agreement; and, on the other hand, a practical need to reconcile waiver declarations. A potential tenant and host agree on the goal; However, the tenant must ensure that his unique mission requirements can be met by the host`s accreditation requirements, with all exceptions granted by the Hostel to uniform security requirements.