CHARTER AMENDMENT

Document Type: 
Collection: 
Document Number (FOIA) /ESDN (CREST): 
CIA-RDP89B01354R000200310022-2
Release Decision: 
RIPPUB
Original Classification: 
K
Document Page Count: 
1
Document Creation Date: 
December 27, 2016
Document Release Date: 
March 28, 2013
Sequence Number: 
22
Case Number: 
Publication Date: 
March 21, 1979
Content Type: 
MEMO
File: 
AttachmentSize
PDF icon CIA-RDP89B01354R000200310022-2.pdf63.93 KB
Body: 
aMON Declassified in Part- Sanitized Copy Approved forRelease2013/03/28 : CIA-RDP89B01354R000200310022-2 DEFENSE 'INTELLIGENCE AUNCY .WASHINGTON. D.C. .20301 TOf Chairman, Computer Security Subcommittee . FROM: DIA Alternate Member SUBJECT: Charter Amendment 21 March 1979 1. The Computer Security Subcommittee (CSS) is a subcommittee of the NFIB Security Committee (SECOM). The CSS is not in itself an NFIB subcommittee but rather works directly for and under the SECOM. In light of this, I feel that attachment 2 of DCID 1/11 is not directive in nature but merely outlines subject areas which may be of concern to the CSS. The MID 1/11 attachment 2, provides a charter for the CSS to operate in various .subject areas when and if tasked to do so by the SECOM. I do not view the CSS role as an active one; where the subcommittee seeks out and attempts solution to perceived problems simply because the problem area exists or is alluded to in the DCID. Personnel resources, as you well know, are scarce and increasing Agency responsibilities dictate that Agency work receive attention as well as Community problems. The CSS should not function as a "quasi" NFIB committee but rather provide expertise and support to the SECOM when requested. Attempting to accomp- lish too much will only result in achieving all too little. 2. Assumption of the communications security role for communications processors will only result in additional areas of concern of which the expertise of CSS members may not be adequate. Communications problems, whether securit,, relatee or strictly operational, would best be left to trained communicators. Certainly, the CSS should not exclude computer networks or ADP systems which provide both a conventional ADP and communications capability. But, I feel the current CSS charter is adequate to meet these cases. 3. I recommend that a closer relationship with our parent committee be developed. If the SECOM wishes the CSS to become involved with areas dealing with communications, appropriate tasking would be initiated and/or Agency coordination accomplished at a much higher level. Declassified in Part - Sanitized Copy Approved for Release 2013/03/28: CIA-RDP89B01354R000200310022-2