[CESG] CESG-P-2019-03-003 Approval to publish CCSDS 350.7-G-2, Security Guide for Mission Planners (Green Book, Issue 2)

CCSDS Secretariat thomas.gannett at tgannett.net
Tue Mar 26 15:35:20 UTC 2019


Dear CESG Members,

Conditions for approval of CCSDS 350.7-G-2, Security Guide for 
Mission Planners (Green Book, Issue 2) have been disposed to the 
satisfaction of the AD(s) who voted to approve with conditions. The 
Secretariat will now proceed with CMC polling to authorize publication.

>From: "Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot at nasa.gov>
>To: "Biggerstaff, Craig (JSC-CD221)[SGT, INC]" <craig.biggerstaff at nasa.gov>,
>         "Weiss, Howard" <Howard.Weiss at parsons.com>,
>         Thomas Gannett
>         <thomas.gannett at tgannett.net>
>Subject: RE: Results of CESG-P-2019-03-003 Approval to publish CCSDS
>   350.7-G-2, Security Guide for Mission Planners (Green Book, Issue 2)
>Date: Tue, 26 Mar 2019 14:46:58 +0000
>
>Craig,
>
>        I agree with your changes and consider the poll 
> conditions/suggestions satisfied.
>
>    Kind regards,
>
>       Jonathan
>
>-----Original Message-----
>From: Biggerstaff, Craig (JSC-CD221)[SGT, INC] <craig.biggerstaff at nasa.gov>
>Sent: Tuesday, March 26, 2019 10:40 AM
>To: Weiss, Howard <Howard.Weiss at parsons.com>; Thomas Gannett 
><thomas.gannett at tgannett.net>
>Cc: Wilmot, Jonathan J. (GSFC-5820) <jonathan.j.wilmot at nasa.gov>
>Subject: RE: Results of CESG-P-2019-03-003 Approval to publish CCSDS 
>350.7-G-2, Security Guide for Mission Planners (Green Book, Issue 2)
>
>Attached are a couple of minor edits to answer Jonathan Wilmot's 
>poll conditions.  "Track changes" is enabled in the document so you 
>can see what was done.
>
>For the first recommendation, I eliminated "dedicated" from the 
>control itself.  Two clarifying sentences were added which list 
>several means of providing functional isolation.
>
>For the second recommendation, I added a new control but located it 
>under "A.12.5 Control of operational software", instead of "A.11.2 
>Equipment" which relates more to physical security.
>
>"A.9.6.MP2
>Space systems should provide an isolated computing environment for 
>critical vehicle control functions, separate from that used for 
>other in-flight computing functions.  Separation may be achieved 
>through various means, such as dedicated physical processing units, 
>hypervisors, or other functional partitioning in hardware and 
>software (e.g. ARINC 653).  Regardless of implementation, the 
>objective is that critical functions should not be vulnerable to 
>disruption due to a failure or breach in non-critical functions."
>
>"A.12.5.MP2
>Space systems should provide the capability to detect modifications 
>to onboard software.  The implementation should provide a means to 
>check hashes or signatures for installed software components and 
>data loads, to verify their integrity against known-good values in 
>run time and/or report these signatures in telemetry."
>
>
>
>
>Craig Biggerstaff
>Senior Engineer Specialist, Mission Systems Operations Contract
>+1 281 483 2027
>craig.biggerstaff at nasa.gov




More information about the CESG mailing list