Notes - MCS
Robust Software
Notes - MCS
Robust Software
  • Robust Software
  • Secure Software Design Principles
    • Motivation
    • Secure and Resilient/Robust Software
    • Best Practices for Resilient Applications
    • Designing Applications for Security and Resilience
    • Architecture for the Web/Cloud
  • Software Security Lifecycle
    • Motivation
    • Secure Development Lifecycle
    • Software Security Touchpoints
    • Software Assurance Forum for Excellence in Code (SAFECode)
    • Secure SW Lifecycle Processes Summary
    • Adaptations of the Secure Software Lifecycle
    • Assessing the Secure Software Lifecycle
    • Recommendations
  • Software Quality Attributes
    • Motivation
    • Software Quality Assurance
    • Software Quality Standards
    • Software Quality Attributes
    • Extra Software Quality Assurance Properties
  • Security Requirements
    • Motivation
    • Security Requirements
    • Threats
    • Defenses
    • Confidentiality
    • Integrity
    • Availability
    • What about other goals/properties?
    • Security Requirements Engineering
    • Types of Security Requirements
    • Security Policy
    • Precision
    • Completeness and Consistency
    • Examples of Non-Functional Requirements
    • Goals and Requirements
    • Measures
    • Requirements Interaction
    • Natural Language Requirements
    • Best Practices
  • Common Software Attacks
    • Objectives
    • 10 Major Cyber-Attacks of 21st Century
    • Software Security Basics
    • Defenses Methods
    • SANS SWAT Checklist
  • Safe Programming
    • Secure Coding Practices
    • Top 10 Secure Coding Practices (CERT/SEI)
    • 7 Pernitious Kingdoms
  • Robustness, PenTest, Fuzzy and Static Code Analysis
    • Security/Robustness Testing
    • Robustness Tests Checklist Example
    • Penetration Testing
    • Penetration Testing Roadmap
    • Tools
    • Fuzz Testing
    • Static Code Analysis
    • Side Channels
  • Safety (and Security)
    • Safety
    • A safety Lifecycle Example
    • Risk Management Process
    • System Definition
    • Hazard Identification and Classification
    • Desk-based Hazard Identification
    • Workshop-based Hazard Identification
    • HAZOP
    • Hazard Identification and Classification
      • Broadly acceptable risks
    • Risk Evaluation and Risk Acceptance
    • Use of codes of practice
    • Use of reference system
    • Explicit risk estimation
    • Qualitative risk estimation
    • Quantitative risk estimation
    • Safety measures
    • Safety requirements
    • Hazard Management
    • Hazard life cycle
    • Independent Assessment
    • Safety Plan
    • Safety Case
    • FMEA Example
    • DevSecOps
Powered by GitBook
On this page
  1. Safety (and Security)

A safety Lifecycle Example

EN 50126:1999 Railway Applications – The Specification and Demonstration Of Reliability, Availability, Maintainability And Safety (RAMS).

  • Published by CENELEC – European Committee for Electrotechnical Standardisation.

  • Provides Railway Authorities and the railway support industry with a process that enables the implementation of a consistent approach to the management of RAMS.

  • Can be applied systematically throughout all phases of the lifecycle of a railway application.

Defines RAMS in terms of reliability, availability, maintainability, and safety and their interaction.

Defines a process for managing RAMS.

Enables conflicts between RAMS elements to be controlled and managed effectively.

Defines a systematic process for specifying requirements for RAMS and demonstrating that these requirements are achieved.

EN 50126 Lifecycle.

  • Is a sequence of phases, each containing tasks, covering the life of a system from initial concept through to decommissioning and disposal.

  • The lifecycle provides a structure for planning, managing, controlling, and monitoring aspects of a system, including RAMS.

Phase
Description

Concept

  • Develop a level of understanding of the system sufficient to enable all subsequent RAMS tasks.

  • Review previously achieved safety performance

System Definition and Application Conditions

  • Define the mission profile of the system and its boundaries.

  • Establish the application conditions influencing the characteristics of the system.

  • Define the scope of the hazard analysis.

  • Establish the Safety Plan.

Risk Analysis

  • Perform System Hazard & Safety Risk Analysis.

  • Set up Hazard Log.

System Requirements

  • Specify the overall System Safety requirements.

  • Establishment of Safety Management

Apportionment of System Requirements

  • Define the RAMS acceptance criteria for the designated sub-systems and components.

  • Apportion System Safety targets and requirements to designated sub-systems and components.

Design and Implementation

  • Create sub-systems and components.

  • Demonstrate that sub-systems and components conform to RAMS requirements.

  • Implement a Safety Plan.

  • Prepare a Generic Safety Case.

Manufacturing

  • Implement a process that produces RAMS-validated sub-systems and components.

  • Use Hazard Log.

Installation

  • Assemble and install the total combination of sub-systems and components.

  • Initiate system support arrangements.

  • Establish Installation Programme.

System Validation

  • Validate that the total combination of sub-systems, components, and external risk reduction measures comply with the RAMS requirements for the system.

  • Commission the total combination of sub-systems, and components risk reduction measures.

  • Prepare, and if appropriate accept the Application Specific Safety Case.

System Acceptance

  • Assess compliance of the total combination of sub-systems and components with the overall RAMS requirements of the complete system.

  • Accept the system for entry into service.

  • Assess Application Specific Safety Cases.

Operation and Maintenance

Operate maintain and support the total combination of sub-systems and components such that compliance with system RAMS requirements is maintained.

Performance Monitoring

  • Maintain confidence in the RAMS performance of the system.

  • Collect, analyze, evaluate, and use performance and Safety statistics.

Modification and Retrofit

  • Control system modification and retrofit tasks to maintain system RAMS requirements.

  • Consider safety implications for modification and retrofit.

Decommissioning an Disposal

  • Control system decommissioning and disposal tasks.

  • Perform hazard analysis and risk assessment.

Last updated 1 year ago