ATTACHED MEMORADUM FROM THE DIRECTOR OF SECURITY DEALING WITH R&D SECURITY PROCEDURES

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP69B00596R000100160025-2
• Release Decision: RIPPUB
• Original Classification: S
• Document Page Count: 2
• Document Creation Date: November 16, 2016
• Document Release Date: February 22, 2000
• Sequence Number: 25
• Publication Date: July 18, 1966
• Content Type: MF

Approved For Release 2000/05/04: CIA-RDP69B00596R00010016.902572 _
25X1A
25X1A
5X1A
25X1A
25X1A
25X1A
7
0162/66
18 July 1966
MEMORANDUM FOR: Executive Officer/DDS&T
SUBJECT
: Attached Memorandum from the
ector of
Security Dealing with R&D Security Procedures
1. Historically the referenced memorax2dum was caused by several
cables from the Director of the Air Force Project on the West Coast 25X1A
e to Agency attempts to sign up his staff for and
access. As a result the DNRO sent over the attached request
(marked basic)asd a survey of the security practices of both the Air
Force and this Agency in the R & D field was conducted by representatives
of the Special Security Center last February.
2. Paragraph Za represents a change from present procedures in that
all contractor clearances will be recorded in the CIA Central
Index. The permissible language "It would save time and money if. .
one could build an clearability previously established. . . is obviously
designed to permit this Agency to continue (without coming right out and
saying it) to take a fresh look at an individual's clearability despite the
fact that he may currently possess an Air Force M=Iclearance.
. Paragraph 2b represents no change from the current practice.
4. Paragraph ac appears to be intentionally ambiguous compared
with the language of 2b. This ambiguity is undoubtedly designed to
encompass those Projects where joint Air Force/CIA access
approval authority has been agreed upon while at the same time countenance
the sole authority of a Program Director managing an activity where such
agreements have not been reached.
Approved For 6eLaSe?2C101) /04 : CIA-RDP69800596ROG0 0014325,2
25X1A
25X1A
Approved For Release 2000/05/04 P69600596R000100160025-2
-2-
0162/66
Copy..4:_of_de_
SUBJECT: Attached M.rroranduin fromthe D/OS dealing with
R&D Security Procedures
25X1A
5. Paragraph Zd app.ar. to be directly responsive to Dr. MOM
request. The NRO will be the repository for the Registry.
6. The language in paragraph Ze "placed under control"
gives no guidance concerning whether an R&D effort would be associated
with an existing operational project, or whether access would be permitted
25X1A for anyone holding any clearance. I believe from * security
clearability standpoint that the latter interpretation is intended.
25X1A
25X1A
25X1A
25X1A
7. Paragraph f approaches,but does not quite come to gripe with,
one of the underlying issues where it says that R&D activities should be
formally entered into the System "where a complete system
is deemed to be feasible:" Undoubtedly the memorandum intends that
the Program Director will be the one who determines feasibility. In
the past this has beenPdebatable point with the Air Force instating that
the DNR.0 must make this decision. Also the words 'formally entered
into the System" does not define how this is accomplished.
am sure it is intended that the present procedures under which. the
Da makes this formal determination will be retained.
c t
Cys 1,2,3
544/6. Cys 1,2
52080/6 Cy 2c
0/DD/S&T:mlf:4006(18 July 1966)
Distribution:
Cy 1 & 2 - Addressee
Cy 3 & 4 - AC/SMS/DDS&T
Cy 5 & 6 - DD/S&T Reg.
AC/SM1/DDS&T
25X1A
25X1A
Approved For Release 2000/05/04: CIA-RDP69600596R0001001600