SDLS Protocol Green Book initiation

Slides:



Advertisements
Similar presentations
Cryptography and Network Security 2 nd Edition by William Stallings Note: Lecture slides by Lawrie Brown and Henric Johnson, Modified by Andrew Yang.
Advertisements

Systems Analysis and Design in a Changing World
<<Date>><<SDLC Phase>>
WKES 3202 SOFTWARE REQUIREMENTS ENGINEERING SEMESTER 1 SESSION 2004/2005.
A summary of the PSS-05 URD template
1 Introduction to System Engineering G. Nacouzi ME 155B.
Applied Cryptography for Network Security
Cryptography and Network Security Chapter 1. Chapter 1 – Introduction The art of war teaches us to rely not on the likelihood of the enemy's not coming,
AD description template definition Marián Mlynarovič FIIT Lectures 2006.
Cryptography and Network Security Third Edition by William Stallings Lecture slides by Lawrie Brown.
Cryptography and Network Security Chapter 1 Fourth Edition by William Stallings Lecture slides by Lawrie Brown.
Dr. Lo’ai Tawalbeh 2007 INCS 741: Cryptography Chapter 1:Introduction Dr. Lo’ai Tawalbeh New York Institute of Technology (NYIT) Jordan’s Campus
Cryptography and Network Security
Eng. Wafaa Kanakri Second Semester 1435 CRYPTOGRAPHY & NETWORK SECURITY Chapter 1:Introduction Eng. Wafaa Kanakri UMM AL-QURA UNIVERSITY
Symmetric Key Management Books Development Plan Daniel Fischer (ESA) Ignacio Aguilar Sanchez (ESA) CCSDS Spring Meeting 2010 | Portsmouth, VA.
Delta-DOR SIG: Report of the Fall 2007 Meeting Heppenheim, Germany October 5th, 2007 Roberto Maddè ESA/ESOC
Software Requirements Engineering CSE 305 Lecture-2.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/SPARTA (a Parsons Company) April.
1 Chapter 8++ The Final Design Report. 2 Motivation The main purpose of the design report is to provide all the information necessary to: The main purpose.
Standards Certification Education & Training Publishing Conferences & Exhibits 1Copyright © 2006 ISA ISA-SP99: Security for Industrial Automation and Control.
Ajh January 2007 CCSDS “Books” Adrian J. Hooke CMC Meeting, Colorado Springs 26 January 2007.
0 CCSDS Systems Engineering Area: Security Working Group Howard Weiss NASA/JPL/PARSONS November 2014 BSI, London.
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
1 Chapter 1 – Background Computer Security T/ Tyseer Alsamany - Computer Security.
Topic 1 – Introduction Huiqun Yu Information Security Principles & Applications.
SDLS Protocol Padding concept Ignacio Aguilar Sanchez (ESA) CCSDS Spring Meeting 2010 | Portsmouth, VA.
Delta-DOR SIG Minutes of the meeting Heppenheim, Germany October 2nd, 2007 Roberto Maddè ESA/ESOC
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
SDLS Protocol Green Book initiation Ignacio Aguilar Sanchez (ESA) CCSDS Spring Meeting 2010 | Portsmouth, VA.
Security WG: Report of the Fall 2003 Meeting October 28, 2003 Howard Weiss, NASA/JPL/SPARTA.
Report Writing Lecturer: Mrs Shadha Abbas جامعة كربلاء كلية العلوم الطبية التطبيقية قسم الصحة البيئية University of Kerbala College of Applied Medical.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Security WG: Report of the Spring 2004 Meeting May 13, 2004 Howard Weiss, NASA/JPL/SPARTA.
The CCSDS Security WG is chartered to:
Future Network Standardization Activities in ISO/IEC JTC1/SC6
INF th of January 2005.
BASIC IRRS TRAINING Lecture 7
Legal Skills 411 Presented by: Chantelle H Louw.
Technical Report Writing
CCSDS Systems Engineering Area: Security Working Group
Literature review Methods
Physical Layer Security
Security WG: Report of the Fall 2013 Meeting
Chapter 18 Formal Reports
Space Data Link Security BOF SEA/SLS October 14, 2008 meeting
CPMGT 301Competitive Success/tutorialrank.com
CPMGT 301 Education for Service--tutorialrank.com.
CPMGT 301 STUDY Lessons in Excellence--cpmgt301study.com.
Object-Oriented Design
Brief Introduction to IEEE P802.1CF
Project Plan Template (Help text appears in cursive on slides and in the notes field)
Introduction to vital statistics report writing
Documenting an Architecture
Systems Analysis and Design in a Changing World, 6th Edition
Cryptography and Network Security
IRRS REFRESHER TRAINING Lecture 4
ATS Architecture Design Solution Intent
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document.
CS 8532: Advanced Software Engineering
, editor October 8, 2011 DRAFT-D
Class Project Guidelines
Building a MACsec Draft
IMT-Advanced Technical Requirements
Design Report Submit one report per sub-team
Research Proposal and Report
Draft Mandate to request SCHER opinion on the TGD-EQS
Concept paper on the assessment of WFD River Basin Management Plans
Cryptography and Network Security
DRAFT ISO 10008:2013 Overview Customer satisfaction — Guidelines for business-to-consumer electronic commerce transactions ISO/TC176 TG 01.
Presentation transcript:

SDLS Protocol Green Book initiation Ignacio Aguilar Sanchez (ESA) CCSDS Spring Meeting 2010 | Portsmouth, VA

Background Green Book definition: Intended to provide for the timely publication of a very broad range of general information for the CCSDS community. Informational documents are often published in support of an Experimental specification, a Draft Standard or a Recommended Standard. They may therefore contain descriptive material, supporting analysis, test results, scenarios, etc., which are otherwise inappropriate for the contents of a technical specification.

Chapter 1 of ToC Introduction Purpose Scope Organization of this Report Conventions and Definitions References Chapter 1 structure is standard. No particular adaptation to SDLS GB.

Chapter 2 of ToC Overview SDLS protocol Motivation A summary description of what is SDLS and how it relates to SDL protocol. Motivation Provides the reasons why such protocol has been developed. Explains the simple mission network topology. Interiperability for cross-support. Major design goals and constraints Security Services Compatibility with SDL Services Compatibility with SLE Services Independence of cryptographic algorithms and support to CCSDS cryptographic algorithms Chapter 2 provides a summary introduction to SDLS.

Chapter 3 of ToC Title to be found (design concepts? Summary of concept and rationale?) Security services (selection) This section will present the rationale for the selection of the agreed security services (authentication, confidentiality, integrity and combinations thereof). The selected services are taken out of ISO OSI Security Architecture. A set of tables (one per SDL protocol) will document threats, risks, and other elements justifying the decision taken for each of those ISO OSI Security Services. An important element of information will be constituted by the residual risk for not implementing a security service or by considering the performance of the selected service. Protocol position This section will present the placement of SDLS with respect to SDL in the CCSDS protocol stacks and its rationale. Furthermore, it will identify and discuss the interfaces with other layers. Protocol data structures, fields and functions Organization and description of the various protocol data structures and fields with their corresponding function. Justifications. Management Presentation and discussion of management aspects. Among other things Security Association and Security Context are treated here. In line with GB template chapter 3 provides a detailed technical presentation and discussion of the major technical decisions behind SDLS development.

Chapter 4 of ToC Concept of Operation Integrates the content produced by CB on the GB Conops. In particular look at cryptographic service processing flow diagrams.

Annexes To be completed Reference implementation ISO OSI Security Services tables vs. SDL protocols URD …. Annexes will document detailed elements of information (e.g., analyses) not suitable for the main body of the document.

Open Points Documenting detailed SDLS requirements? A summary of main requirements and their discussion will go into the GB. Should in addition detailed requirements be available for the reader? If so a reference can be made to the URD but the URD would need to be available (i.e., published) at www.ccsds.org. Alternatively, the URD becomes an Annex to this GB Any relevant experience in previous GBs?

Next Actions Collect feedback on the meeting and afterwards Coordinate with SDLS Blue Book Technical Editor (Craig) to harmonize contents Assign content writers on agreed topics