1. November 20041 SECURITY WORKING GROUP REPORT November 2004

2. 2 AREA REPORT CONTENTS A.CURRENTLY ACTIVE WGs AND BOFs WITHIN AREA B.SUMMARY TECHNICAL STATUS OF EACH WG & BOF C.CROSS-AREA TECHNICAL ISSUES D.OTHER ISSUE AND CONCERNS E.PROPOSED AREA RESOLUTIONS/ACTION ITEMS

3. November 20043 1.xxx WG Fill in numbered list A.LIST OF CURRENT WGs AND BOFs WITHIN AREA AREA REPORT

4. November 20044 B.SUMMARY TECHNICAL STATUS 1.SECURITY WG Goal: The Security WG is developing security guides (e.g., Security Green Book, Threat Document) and security standards (e.g., encryption, authentication) for CCSDS. In addition, it is providing security advice and guidance to other working groups. Working Group Status: Active _X__ Idle ____ Working Group Summary Situation: Working Group Summary progress: The SecWG has revised the Security Green Book and has generated another revision of the Threat Document and the Security Architecture. The SecWG has also worked with the Cross Support Services Area to create the mandatory security sections for the SLE red books as well as the creation of a security annex specifying the security details for SLE. Problems and Issues: The usual problem of resources. Many people are “assigned” to the SecWG but few have the funding to do more than review materials. If we had more member participation, more of the “new” work items could be accomplished sooner, and in parallel with existing work items. status:OKCAUTIONPROBLEM comment: Work items are in development although behind schedule AREA REPORT

5. November 20045 A.Issue 1 Accomplishment: Cross Support Services - aided in the creation of the mandatory security section for the SLE red books as well as the revised security annex. B.Issue 2 Meeting with SLS: SecWG met with SLS at an SLS plenary session to discuss SecWG work items. SLS is very concerned with physical layer security – which the SecWG lacks expertise in. SLS is also concerned with obtaining physical layer security requirements. Also, there is a question as to whether there are CCSDS requirements for security interoperability which would require prescriptive security architectures rather than the current “menu-based” security architecture. C.CROSS-AREA TECHNICAL ISSUES AREA REPORT

6. November 20046 D.OTHER ISSUES AND CONCERNS A.Issue 1 Fill in numbered list of any other issues and concerns (resources,etc.) B.Issue 2 AREA REPORT

7. November 20047 E.PROPOSED RESOLUTIONS AND ACTIONS FOR CESG/CMC APPROVAL RESOLUTION 1 : AREA-[WG-]R-0411-001 Considering that: 1.CCSDS has no security standards, And recognizing that: 1.CCSDS is much more concerned with security for its missions, The AREA resolves that: CCSDS provide the resources to develop encryption and authentication/integrity standards which are fully adapted to the space community and have been profiled, implemented, and tested before becoming CCSDS recommended standards ACTION ITEM 1: AREA-[WG-]A-0411-001 Request that the CMC provide adequate resources to accomplish this in accordance with XXX. ACTION ITEM 2: AREA-[WG-]A-0411-002 (statement of derived Action2, who assigned to and due date) AREA REPORT