CAVWAYs
  • Home
    • News Clips
  • Intro
    • COVID-19 Impact
    • Differences
    • Other Systems
    • CAV producer
    • State planner
    • Traveler
    • Trucker
    • Transport-service provider
    • Environmentalist
    • Skeptic
  • Davius' Commandments
  • In the Beginning
    • Mass Transit in California
    • Freeway Challenges
  • Reuse
  • Public-Private Sectors
    • Internet Example
  • System Engineering
    • Requirements
    • Design
    • Development
  • CAV Systems
    • Controlled Space
    • Roadway Conditions
    • Concept of Operations
    • CAVWAY Components
    • CAVs
    • CAV Requirements
  • CAV System Qualities
    • Safety
    • Efficiency
    • Security
    • Privacy
    • Accessibility
    • Sustainability
    • Maintainability
  • Common Protocols
    • Change Lanes
    • Routing
    • Coordination
  • Prototype
    • CSIM Objectives
    • CSIM Implementatiion
    • CSIM Scenarios
  • Reservations
  • Transition
    • Instrumented CAVWAYs
    • Dual-Mode Vehicles
    • Early CAVWAYs
    • Full automation & Partition
  • The Big C
  • Summary

Security

A few specifics

Why emphasize CAV-System security?
For CAV Systems to be safe, they will have to be secure from external interference and threats. Security will be designed into CAV Systems such that people with malicious intent are kept out and human travelers and freight are kept safe from vandals and criminals. A critical security goal is to minimize the likelihood of any individual or group gaining direct control of a CAV System.
Measures of Security
One measure is the number of security violations detected. Violations would fall into various categories such as minor (safety not compromised in any way), serious (an intruder was able to violate system security boundaries and access sensitive information), and catastrophic (an intruder was able to gain control of all or part of a CAV System requiring system shutdown).
Achieving CAV-System Security
CAV-System security features would include 1) common CAV protocols to obviate the need for central control, and 2) CAV autonomy to reduce the risk of external intrusion. Two CAVNET physical-layer features will reduce vulnerabilities and opportunities to hack the network: first, CAVNET will be a private network, inaccessible from public networks such as the Internet; second, radio-based signals will use techniques such as anti-jam [Imperial Eagle DWC. 2021] and low probability of intercept frequency hopping [Stevens, D.L. 2016].

In addition to his eighth commandment at right, Davius has these thoughts about security:
1) hide vulnerabilities, such as nerves and nerve-centers,
2) eliminate single points of failure,
3) reinforce trust by using redundancy and autonomy to validate decisions, and
4) recognize that security is generally gained through inconvenience.
More ideas in the column at right.

Davius' Eighth Commandment
Use isolation and autonomy to buy security.
That Davius should offer relatively little guidance in this area is not surprising since hackers and vandals offered little threat to the control of Roman Roads. The concept of a controlled space was solid, but controlling that space seldom appeared beyond the capability of Roman Armies. What follows are clues to how CAV Systems will observe Davius' general security guidance.
Hiding vulnerabilities
CAVNET, which links CAVs and Corridor nodes, will not be accessible through any public network connections (such as the Internet). To disrupt the CAVNET backbone, a hacker will need to connect directly to the land line, meaning that it would probably have to be an "inside job." Alarming the hardware will diminish the likelihood of this type of crime.
To disrupt a major part of the wireless network, composed of short-distance, anti-jam links, a hacker would need to coordinate efforts across a relatively long distance; for this to go undetected for more than a few seconds is expected to be unlikely. Moreover, such disruptions will, in most cases (such as health-status messages lost), be relatively benign.
No single points of failure
The clean separation between CAVWAY and CAV functionality, indirect CC control through message and protocols, and CAV autonomy will prevent the CAVWAY from forcing any CAV to make an unsafe maneuver. These design features enforce CAV-System security, minimizing the risk of a system takeover.
Reinforcing trust
Double checks on CAV maneuvers and Triple Modular Redundancy of CAVWAY Control (CC) nodes, will further reduce single points of failure.
Security requires inconvenience
This general insight - for example, locking your front door offers security which is gained at the inconvenience of carrying a key or memorizing a code - applies to the separation of CAVNET from public communications networks.
The malicious threat
According to Davius, the danger to our country may be growing. Externally, two violent dictatorships have effectively revived Cold-War rivalries. In Europe, one has launched a murderous war. The other dictatorship threatens to do the same in Asia. At home, guns and violence are more than ever a part of our daily and political lives. Meanwhile, we struggle to move clear of the recent pandemic while confronting unusually high monetary inflation.

Powered by Create your own unique website with customizable templates.
  • Home
    • News Clips
  • Intro
    • COVID-19 Impact
    • Differences
    • Other Systems
    • CAV producer
    • State planner
    • Traveler
    • Trucker
    • Transport-service provider
    • Environmentalist
    • Skeptic
  • Davius' Commandments
  • In the Beginning
    • Mass Transit in California
    • Freeway Challenges
  • Reuse
  • Public-Private Sectors
    • Internet Example
  • System Engineering
    • Requirements
    • Design
    • Development
  • CAV Systems
    • Controlled Space
    • Roadway Conditions
    • Concept of Operations
    • CAVWAY Components
    • CAVs
    • CAV Requirements
  • CAV System Qualities
    • Safety
    • Efficiency
    • Security
    • Privacy
    • Accessibility
    • Sustainability
    • Maintainability
  • Common Protocols
    • Change Lanes
    • Routing
    • Coordination
  • Prototype
    • CSIM Objectives
    • CSIM Implementatiion
    • CSIM Scenarios
  • Reservations
  • Transition
    • Instrumented CAVWAYs
    • Dual-Mode Vehicles
    • Early CAVWAYs
    • Full automation & Partition
  • The Big C
  • Summary