Safety Manual#
Note
Document header
[Your Module Name] Safety Manual
|
status: draft
security: YES
safety: ASIL_B
|
||||
Attention
The above directive must be updated according to your Module.
Modify
Your Module Nameto be your Module Name or put “Platform”Modify
idto be your Module Name in upper snake case preceded bydoc__and succeeded bysafety_manualAdjust
statusto bevalidAdjust
safetyandtagsaccording to your needs
Introduction/Scope#
Assumed Platform Safety Requirements#
Assumptions of Use#
Assumptions on the Environment#
List of AoUs expected from the environment the platform / module runs on:
Title |
ID |
Status |
|---|---|---|
Another Title |
invalid |
|
Build environment supports Rust 2021 |
valid |
|
Confidentiality of Persisted Data |
valid |
|
External Health Management |
valid |
|
File System |
valid |
|
KVS Limits Configuration |
valid |
|
OS safety functions |
valid |
|
Persistency Error handling |
valid |
|
pkcs11_dynload: Integrity and authenticity of the pkcs11 module |
valid |
|
pkcs11_dynload: No use of ALLOW_PKCS11_LIB_OVERRIDE |
valid |
|
POSIX Operating System |
valid |
|
Process Isolation |
valid |
|
Read-only Default Values |
valid |
|
Safe HW platform |
valid |
|
Storage Access Rights |
valid |
|
Vehicle time end-to-end integrity |
valid |
Attention
Make sure these AoU are here for a safety reason, i.e. every one “mitigates” a safety analysis entry.
Assumptions on the User#
List of AoUs on the user of the platform or the module of this safety manual:
Note: Platform safety manual collects all platform wide AoU (have to be fulfilled by the user for any feature). Module safety manual collects all AoUs specific to a feature and its realizing components. This means for every feature the user selects, the platform safety manual and the related module manual has to be considered.
Title |
ID |
Status |
|---|---|---|
Access control |
valid |
|
Applications relying on logs verification/qualification/case. |
valid |
|
aragen not safe |
valid |
|
Avoidance of Exceptions |
valid |
|
Avoidance of heap allocations after initialization |
valid |
|
Backend initialization by the user |
valid |
|
Bazel tooling |
valid |
|
Bitmask Enum Value Constraints |
valid_inspected |
|
Bug fixing |
valid |
|
Bug interface |
valid |
|
C++ Library Preference |
valid |
|
Check Capacity |
valid |
|
Check for nullptr on Allocate() |
valid |
|
Checking for possible message overflow |
valid |
|
Client Registration as First API Call |
valid |
|
Config on a safe filesystem |
valid |
|
Configuration from timing analysis |
valid |
|
Console Logging |
valid |
|
Container State Verification |
valid |
|
Cooperative Cancellation Handling |
valid |
|
Correctly configured ASIL Level |
valid |
|
Correctly configured events/fields per service type |
valid |
|
Correctly configured maximum number of maximum elements per subscriber |
valid |
|
Correctly Configured Maximum Number of Subscribers |
valid |
|
Different user for ASIL and QM processes |
valid |
|
Element Lifetime and Ownership |
valid |
|
Element Type Requirements |
valid |
|
Error Domain Implementation |
valid_inspected |
|
Error Handling |
valid |
|
Error Reaction |
valid |
|
Error Reaction and Safe State |
valid_inspected |
|
Evaluation thread scheduling |
valid |
|
Event or Field reception via GenericProxy needs specific care |
valid |
|
Event Subscription active while holding SamplePtr |
valid |
|
External Synchronization Required for Concurrent Access |
valid_inspected |
|
Fault tolerant time budget |
valid |
|
FEO something |
invalid |
|
FEO something |
invalid |
|
FlatBuffers access control |
valid |
|
FlatBuffers buffer verification before access |
valid |
|
FlatBuffers buffer version check before access |
valid |
|
FlatBuffers data integrity |
valid |
|
Flush of Safety Relevant Changes |
valid |
|
gPTP Shared Memory Availability |
valid |
|
Hardware Timestamping Support |
valid |
|
Host application integrity |
valid |
|
Index Bounds Checking |
valid |
|
Integral Type Constraints |
valid_inspected |
|
Integrate as Rust library API |
valid |
|
Integration assistance |
valid |
|
Integration levels |
valid |
|
Integration manual |
valid |
|
Integrator safety anomaly reporting |
valid |
|
Integrator safety confirmation |
valid |
|
Iterator Validity |
valid |
|
JSON data integrity |
valid |
|
Launch Manager alive reporting cycle |
valid |
|
Launch Manager alive supervision |
valid |
|
Logging During the C++ Static Storage construction and destruction. |
valid |
|
LoLa Memory only accessed through LoLa |
valid |
|
LoLa specific QNX Messaging End-Points only accessed through LoLa |
valid |
|
Low-Level Use Only |
valid |
|
Memory Management on Task Submission Failure |
valid |
|
Memory Resource Management |
valid |
|
Minimal Process Privileges |
valid |
|
Monotonic clock provision |
valid |
|
Monotonic Semi-Dynamic Memory Allocation |
valid |
|
Network Interface Configuration |
valid |
|
Next Title |
invalid |
|
No APIs from Implementation Namespace |
valid |
|
No Copy-Send() while holding AllocateePtr. |
valid |
|
No guarantee in availability of services |
valid |
|
No guarantee on execution time |
valid |
|
No guarantees for notifications |
valid |
|
No mixed ASIL |
valid |
|
No notification on termination of producer |
valid |
|
No Protection against Intentional Manipulation |
valid |
|
No Root Privileges |
valid |
|
No shared memory allocation in namespace lola |
valid |
|
No static context support |
valid |
|
No test stubs in production |
valid |
|
No Trace API Usage During Static Initialization / Destruction |
valid |
|
Non-Terminating callbacks |
valid |
|
None reentrant methods per event instance |
valid |
|
on_target_crates |
invalid |
|
One producer only one AllocateePtr |
valid |
|
Only LoLa supported types |
valid |
|
OS Public API Use |
valid |
|
Path Validation |
valid |
|
Performance |
valid |
|
pkcs11_dynload: pkcs11.h compatiblity |
valid |
|
Program Flow Monitoring |
valid |
|
Quality of data is dependent on producer |
valid |
|
Read-Only Shared Memory Objects |
valid |
|
Resource Lifetime |
valid_inspected |
|
Result Value Handling |
valid_inspected |
|
RST-0001 |
valid |
|
RST-0002 |
invalid |
|
rust_core_lib |
valid |
|
rust_std_lib_modules |
invalid |
|
Safe OS Function Use |
valid |
|
Safety anomaly reporting |
valid |
|
Safety AoU |
valid |
|
Safety functions |
valid |
|
Safety integration |
valid |
|
Safety matching |
valid |
|
Same compiler settings for provider and consumer side |
valid |
|
Separate KVS Instances per Software Element |
valid |
|
Shared Memory Permissions |
valid |
|
Single Instance per Interface |
valid |
|
Single Publisher Process |
valid |
|
Skeleton alive while its AllocateePtr being used |
valid |
|
Start before running |
valid |
|
Start without Persisted Data |
valid |
|
Success Expected |
valid |
|
Supported Path Formats |
valid |
|
SW-platform integration bug reporting |
valid |
|
SW-platform test completion |
valid |
|
SW-platform testing |
valid |
|
Thread Pool Sizing |
valid |
|
Thread Safety |
valid_inspected |
|
Thread Safety |
valid |
|
Thread Safety |
valid |
|
Thread Safety |
valid |
|
Trace API Return Values Not for ASIL B Decisions |
valid |
|
Trace Done Callback Thread Safety |
valid |
|
Undocumented or Private APIs |
valid |
|
Unit test execution across build configurations and target systems |
valid |
|
Unsupported Contexts |
valid |
|
unsupported data-types |
valid |
|
Usage of configuration "oversubscription" |
valid |
|
Valid callbacks while proxy alive |
valid |
|
Validity of pointer on LoLa pointer |
valid |
|
Vehicle time end-to-end integrity |
valid |
Attention
Make sure these AoU are here for a safety reason, i.e. every one “mitigates” a safety analysis entry.