1 / 9

Certification

Learn about the certification mandates for Mac Mollison, including FAA standards, DO178B and DO297, and the role of organizations like DoD and NSA in certifying crypto software and devices.

jjavier
Download Presentation

Certification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Certification Mac Mollison

  2. Who mandates certification? • FAA (Federal Aviation Administration) • Standards DO178B, DO297 • DoD (Department of Defense) • Mandates a security validation program incorporating many standards • NSA (National Security Agency) • Certifies crypto software and devices

  3. DO 178-B • Sets lots of “software engineering” rules • E.g., documenting the design/development process • We won’t discuss this further here • Gives criticality levels for software • The only part that has interesting implications for us, to my knowledge • See next slide

  4. DO 178-B Criticality Levels • A: Catastrophic • B: Hazardous • C: Major • D: Minor • E: No Effect

  5. Implications of DO 178-B • Increasing WCET pessimism with increasing criticality level • Our group has written papers on how to deal with this “intelligently” • Need to use Level-A RTOS that forces independence between software of different levels • Defined by ARINC 653 API standard

  6. ARINC 653 • Defines API for time-space partitioning • See next slide • Multiple RTOSs are ARINC 653 compliant • Wind River VxWorks 653 • Etc.

  7. Time-Space Partitioning • Partitions are basically “containers” that are statically scheduled.

  8. DO 297 • Standard for integrated modular avionics (IMA) • Satisfied by using an ARINC 653 OS • Isn’t talked about much and we won’t discuss it further now

  9. Security • Must use “secure” RTOS, hardware, etc. when working with classified information • Classified = confidential, secret, top secret/SAR • Typically, when multiple security levels co-exist in one system, time-space partitioning is used • E.g. VxWorks MILS: Like VxWorks 653, but fewer LOC • More details in security segment of course

More Related