SUMMARY OF 15 MARCH 1984 MEETING

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP86M00017R001501130017-0
• Release Decision: RIPPUB
• Original Classification: U
• Document Page Count: 8
• Document Creation Date: December 22, 2016
• Document Release Date: June 22, 2009
• Sequence Number: 17
• Publication Date: March 16, 1984
• Content Type: MEMO

Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0 42e
-
23 MAR 1984
DIRECTOR OF CENTRAL INTELLIGENCE
Intelligence Information Handling Committee
WASHINGTON, DC 20505
LOGGED.
IHC/CIRS 84-01
16 March 1984
MEMORANDUM FOR: CIRS Management Coordination Group Members
FROM:
CIRS Coordinator
SUBJECT: Summary of 15 March 1984 Meeting
STAT
1. An observer from the DCI's HUMINT Committee will attend all meetings
Committeeimplementation
of the oIeManagement
Groupof
of theCoordination
t
DCI-approvedGroup STIC/HUMINTcoordinate
the recommendations
report.
2. Monthly meetings of this group will be scheduled for the 2nd
Wednesday of each month.
3. The IHC's Telecommunications (TELECumiteewill be requested
to tract the internetting of the COINS and DODIIS networks per
statement at Attachment 1. It was suggested that a COINS representative or a STAT
COINS telecommunications consultant work with appropriate members of the IHC's
TELECOM Subcommittee on this task.
4. NPIC, noted that the full text search and document
retrieval capability for the NDS will not be im lemented until March 1989 vice
the past CIRS planning date of September 1987. agreed to help identify a STAT
point of contact on the COMIREX staff regarding the COMIREX topics as a point
of contact to work the CIRS subject code area. 0 also agreed to provide STAT
further information on NDS future capabilities. It was requested that
individual milestones be shown in the CIRS schedule for the DODIIS and COINS
network implementation including related items not specifically required for
CIRS.
5. Following a general discussion of past work in this area, it was
agreed that the CIRS Standard Concept Code Working Group should meet on
30 March, perform a detailed review of the past efforts
smithis area,
an dGroup
provide a recommended plan of action to the CIRS Management
at our 11 April 1984 meeting. It was also recommended that the assessment to
be provided to the IHC by September 1984 (Attachment 2) not be limited to a
technical feasibility; but incorporate a technical, policy, and resource
assessment.
6. The past efforts of the CIRS Security Working Group were reviewed,
problems were identified, and the proposal made to the IHC at Attachment
3) was discussed. It was noted that the agency IHC representatives must
address this proposal. The proposed future tasking for the CIRS Security
Working Group (Attachment 4) was summarized.
STAT
UNCLASSIFIED
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
7. The proposed Common User Interface (CUI) was briefly discussed. The
assumptions for CUI analysis (Attachment 5) were reviewed. It was requested
that any clarification of the assumptions be provided at the next meeting
(preferably in written form). It was agreed that the FY 86 funding wedge for
this effort at FTD CIRC was appropriate as an interim solution, but that
further coordination of this effort was needed with the DODIIS NQL and COINS
ADAPT work.
8. It was recommended that a formal proposal be made to the IHC to
include D-SAFE as the Phase III node of CIRS and that a SAFE project
representative become a member of the CIRS Management Coordination Group.
9. It was requested that each of the components involved in the CIRS
effort develop a 5-year milestone plan and funding estimate along the lines of
the plan developed by for NSA's implementation tasks.
10. At the next meeting of the group, the following items will be
addressed:
o an overview of the STIC report recommendations;
o the CUI proposed by and recommendations for modifications;
o the proposed plan of action developed by the CIRS Standard Concept
Code Working Group; and
o the 1984 tasks to be addressed by the CIRS Management Coordination
Group and the support requested by an external contractor.
Attachments: a/s
Distribution:
STAT
STAT
STAT
STAT
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
Attachment 1
1 March 1984
PROPOSED TASKING STATEMENT FOR
IHC TELECOMMUNICATIONS SUBCOMMITTEE
Request that your subcommittee review the requirements stated in the CIRS
documentation and report to the CIRS management coordination group and to the
IHC on the following:
o The ongoing status of efforts to implement the DODIIS network by mid-
1986 including a summary of any problems that may prevent the DODIIS
network from being implemented by that date.
o The ongoing status of efforts by appropriate organizations (either DIA
and/or DODIIS users) to implement the user/server protocols that will be
necessary to transition the current IDHSC II user to the new network.
Please specify when the organizations will complete their efforts so
that the network can be fully implemented to insure that all authorized
DODIIS components will have CIRS access.
o The ongoing status of the gateway development efforts between the COINS
II and DODIIS networks and the transition of COINS II to the IP/TCP
protocol. Please specify when these efforts will be complete to the
degree that.COINS users can access CIRS host processors that are tied to
the DODIIS network.
o Recommendations for action on what can be done to meet communications
deadlines or to solve problems identified through the above analyses.
o Request a preliminary report on these items by 15 July 1984 followed by
periodic updates on the status of efforts.
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
Attachment 2
2 March 1984
PROPOSED TASKING STATEMENT FOR
CIRS STANDARD CONCEPT CODE WORKING GROUP
The CIRS Standard Concept Code Working Group will include agency
representatives who are responsible for the development and maintenance of
agency-unique subject/concept codes. This working group will be supported by
a contractor and tasked to do the following:
o Provide a quantitative analysis of the frequency of use of agency-
unique codes over an identified time period (both in coding and in
actual usage for retrieval purposes).
o Compare the structure and content of the various subject codes to
identify the relationships and variations in the schemes.
o Perform an analysis and make a recommendation to the IHC regarding the
possible use of numerical designators for the subject codes versus the
possible use of alphabetic mnemonics.
o Develop a preliminary draft for a standard set of codes by assessing
the relationship and structure of the various codes as well as the
frequency of use of these codes using approximately 100 standard codes
as a guideline for development.
o Evaluate alternatives and recommend to the IHC the most feasible
approach for the use of the standard concept codes (e.g., double
coding of standard codes in addition to agency-unique codes,
translations tables, or Community's adoption of the standard code.
o Coordinate the proposed standard with appropriate elements of the
Community through the IHC.
o Develop the "standard" set of codes and recommend to the IHC an
implementation plan for phasing in the use of code.
o Provide a assessment of the IHC by September 1984 regarding the
feasibility of use of standard concept codes in the CIRS environment.
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017R001501130017-0
Attachment 3
PROPOSED IHC ACTIONS
CONCERNING THE
CIRS SECURITY WORKING GROUP
? APPROVE STAGE I SECURITY REQUIREMENTS (CONTINGENT UPON FINAL
MODIFICATIONS AGREED TO BY IHC MEMBERS) AS THE PRELIMINARY CIRS
SECURITY PLAN FOR PHASE I IMPLEMENTATION
? AUTHORIZE CONTINUING EFFORT BY THE CIRS SECURITY WORKING GROUP TO:
REVISE STAGES II AND III OF THE SECURITY PLAN IN ORDER TO ACHIEVE
COMPARTMENTED MODE OPERATIONS BY 1988
- PREPARE AND UPDATE AS NEEDED DATA CONCERNING RESOURCE NEEDS AND
SCHEDULES FOR THE SECURITY PLAN
APPROVE THE DEVELOPMENT OF A SEPARATE SECTION IN THE CIRS SECURITY PLAN
ADDRESSING MINIMUM ACCEPTABLE SECURITY REQUIREMENTS FOR THE NETWORKS
INVOLVED
Approved For Release 2009/06/22 : CIA-RDP86M00017R001501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
% Attachment 4
PROPOSED TASKING STATEMENT FOR
CIRS SECURITY WORKING GROUP
FOR THE PERIOD MAR 84 - JAN 85
The CIRS Security Group will include agency/component representatives who
are responsible for the security policies and procedures of computer systems
and networks to be used in accordance with the CIRS plan. This working group
will be supported by contractor/consultants and be tasked to do the following:
- The CIRS Security Working Group will continue to review and stay
abreast of developments at CIRS nodes and networks in the following
areas:
o Current security procedures of existing automated systems/data
communications networks which will provide processing services
under the CIRS plan highlighting variations in hardware, software,
and procedural approaches (e.g., password protection, host control
access procedures, terminal identifiers).
o Future security procedures to be incorporated in systems/networks
such as SAFE, COINS, and the DODIIS DNSIX model as well as any
future changes to security in current processors.
o Devices performing specialized security functions, including but
not limited to RECON GUARD and DIA's fingerprint recognizer.
o Phased security enhancements which will be required for the
protection of "G," EXDIS, and LIMDIS materials. Attention will be
focused on how current systems and proposed updates will control
access to these materials (e.g.., how CIA and DIA SAFE will handle
them in the future).
- The Security Working Group will continue to develop information
dealing with CIRS security requirements implementation at the various
CIRS components. Emphasis will be phased on implementation schedules
and the costs/resource requirements needed to achieve the security
up ra es.
- The Security Working Group will review the requirements in the CIRS
Security Plan for network and inter-network security. This review
should result in a separate network section of the security plan
containing these requirements and the associated milestones or
security development stages for these networks and gateways.
- The efforts of the Security Working Group will be concentrated on CIRS
security requirements for Stages II and III as given in the draft CIRS
Security Plan.
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
o Assisted by the IHC staff and contractor/consultants, continue the
development of a final security plan for the overall CIRS effort
incorporating minimum security features that each host and network
must maintain in order to provide the specified services under the
CIRS plan.
o Provide continual review and update of the CIRS Security Plan on a
periodic basis.
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0
 Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0 ttachment 5
ASSUMPTIONS FOR CUI ANALYSIS
? ANALYSTS WANT UNIFORM RETRIEVAL CAPABILITY; INTERACTIVE ACCESS;
EASY TO USE (I.E., NO MANUALS)
? NSA AND FTD CIRC WILL BE OPERATIONAL IN APRIL 1986 WITH
NON-UNIFORM RETRIEVAL CAPABILITIES
? NSA IS TIED TO COINS/ADAPT; FTD CIRC TO BE TIED TO DODIIS/NQL
IN FY86/FY87
? DODIIS USERS CANNOT ACCESS COINS ADAPT; COINS USERS CANNOT ACCESS
DODIIS NQL
? DODIIS NQL WILL NOT BE ABLE TO HANDLE SAFE-D TEXT FILES UNTIL FY87
? DODIIS NQL AND PROBABLY COINS ADAPT WILL CONTINUE TO BE BASED ON
QUERY/RESPONSE OPERATIONS WHICH WILL DELAY CIRS USER RESPONSE TO
APPROXIMATELY 30 SECONDS ON AVERAGE
? THE FIVE MAN-YEAR WEDGE FOR PROVIDING THIS INTERIM CAPABILITY IS
WORTH THE EFFORT TO PROVIDE A UNIFORM CAPABILITY TO THE ANALYSTS
STAT
STAT
Approved For Release 2009/06/22 : CIA-RDP86M00017RO01501130017-0