Csc5113c Review

However, for the systems programmer, the ISA is the law.

CSC5113C – Advanced Topics in Cyber-Physical Systems (CPS) Security Author: [Your Name] Date: April 14, 2026 csc5113c

| Attack Class | Mechanism | Physical Outcome | | :--- | :--- | :--- | | | Flood the control loop with low-priority network traffic, causing control tasks to miss deadlines. | Rotor overspeed, chemical overflow. | | Time-Dilation Spoof | Replay old sensor data with manipulated timestamps, stretching the perceived duration of an event. | ABS system brakes too early/late. | | Resonance Injection | Inject control signals at the natural frequency of a physical process (e.g., bridge, power line). | Cascading failure via harmonic excitation. | However, for the systems programmer, the ISA is the law

When we write code in a systems language like C, we are essentially drafting a blueprint that the hardware must execute directly. Unlike managed languages (like Java or Python) that rely on a Virtual Machine to handle memory and safety, C exposes the raw capabilities—and the sharp edges—of the underlying architecture. | | Time-Dilation Spoof | Replay old sensor

Computer architects now pack multiple cores onto a single die. They introduce complex features like Out-of-Order Execution and Branch Prediction to squeeze instruction-level parallelism. Yet, to utilize these cores, systems programmers must grapple with concurrency models—pthreads, mutexes, and atomic operations.