0% found this document useful (0 votes)
21 views19 pages

Assignment 1 Cloud IoT Enterprise Security

The document outlines the architecture and objectives of Vehicle-to-Everything (V2X) communication systems, emphasizing their potential benefits such as improved road safety and reduced traffic congestion. It also discusses challenges including security threats, standardization, and the need for reliable communication. The conclusion highlights the importance of collaboration among stakeholders to address these challenges for a safer transportation future.

Uploaded by

Oracle Java
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views19 pages

Assignment 1 Cloud IoT Enterprise Security

The document outlines the architecture and objectives of Vehicle-to-Everything (V2X) communication systems, emphasizing their potential benefits such as improved road safety and reduced traffic congestion. It also discusses challenges including security threats, standardization, and the need for reliable communication. The conclusion highlights the importance of collaboration among stakeholders to address these challenges for a safer transportation future.

Uploaded by

Oracle Java
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Cloud, IOT and Enterprise Security

Assignment – I

NAME : RAJASEKAR PV
BITS ID - 2023MT13122
Components of the system
1. In-vehicle network: The systems inside the vehicle, including sensors, controllers, and communication

modules.

2. Communication systems: Between vehicles (V2V), vehicle to infrastructure (V2I), and vehicle to

everything (V2X).

3. Backend services: Remote servers for data processing, updates, and system monitoring.

4. User interfaces: Applications or systems that interact with users or vehicle owners.
Objectives of the System
 Vehicle-to-Vehicle (V2V):
 Vehicles can directly communicate with each other, sharing information
about their speed, direction, and braking status. This can help prevent
accidents by allowing vehicles to react to potential hazards sooner.
Objectives of the System - Continued
 Vehicle-to-Infrastructure (V2I):
 Vehicles can communicate with infrastructure like traffic lights, road
signs, and traffic management systems. This can help optimize traffic
flow, improve safety, and reduce congestion
Benefits of V2X
 Improved Road Safety: V2X can help prevent accidents by enabling vehicles to

react to potential hazards sooner.

 Reduced Traffic Congestion: V2X can help optimize traffic flow by providing real-

time traffic information and enabling vehicles to coordinate their movements.

 Enhanced Driving Experience: V2X can provide drivers with valuable information

and alerts, making driving safer and more convenient.

 Reduced Environmental Impact: V2X can help reduce fuel consumption and

emissions by optimizing traffic flow and enabling more efficient driving.


Challenges of V2X:
 Security and Privacy: V2X systems must be secure to protect against cyberattacks

and ensure the privacy of user data.

 Standardization: There needs to be a common standard for V2X communication to

ensure compatibility between different vehicles and infrastructure.

 Cost: Implementing V2X technology can be expensive, especially for older

vehicles.

 Infrastructure: V2X requires a robust infrastructure of sensors and communication

networks to function effectively.


High Level Architecture – Layered View
Layered Architecture Explained
 The layered architecture is used to give the various layers for the defined high-level architecture.

 The sensing layer is responsible for capturing the inputs/parameters from the environment, the

actuators are responsible for steering and controlling the vehicle based on the sensing devices like

cameras, road condition etc.

 The data captured is sent to the gateway layer where the captured data is relayed to the

application layer.

 The application layer is responsible for processing the data and provide various dimensions for the

various stake holders who are interested in the vehicle-to-vehicle communication etc.

 There are cross cutting layers like monitoring/logging and security which is applicable across all the

layers i.e sensing, gateway and the application layer in the defined architecture.
Security considerations / Threat Landscape
 The threat landscape for connected vehicle IoT systems is complex and constantly

evolving. Here are some of the key threats:

1. Hacking and Remote Control:

Vehicle Takeover: Hackers could gain unauthorized control over critical vehicle

functions like steering, braking, or acceleration, potentially leading to accidents.

Data Theft: Sensitive personal information stored in the vehicle's systems, such as

driver profiles, location data, and financial information, could be stolen.

Ransomware: Hackers could encrypt critical vehicle systems and demand a

ransom for decryption, rendering the vehicle inoperable.


Security considerations - Continued
2. Supply Chain Attacks:

Malicious Components: Malicious software or hardware components could be introduced during the

manufacturing or supply chain process, compromising the security of the vehicle.

3. Network Attacks:

Man-in-the-Middle Attacks: Hackers could intercept communication between the vehicle and other systems to

steal data or inject malicious commands.

Denial-of-Service (DoS) Attacks: Overloading the vehicle's network or cloud services to disrupt connectivity and

functionality.

4. Physical Attacks:

Tampering with Hardware: Physical access to the vehicle could allow attackers to tamper with hardware

components or install malicious devices.


Security Architecture Explained – End to End System in
a Security Perspective
Rational behind the solution
 The security is implemented in the various layers. Its not redundancy rather
helps us to prevent the attacker to intrude into the system by putting various
barricades inside our system.
 The Security is implemented at Vehicle level, Gateway level,
Application/service level.
 We protect the data on transit via the TLS/HTTPS protocol from the Gateway to
Cloud communication.
 The messaging queues like Kafka is used to stream the data of various vehicle
and take decisions at the real time.
 The data at rest that is at the database level the data is protected using the
Scrypt/Bcrypt protocol.
 The Vehicle is constantly communicated by the backend system in case of any
emergencies/updates to be given to the vehicle from the backend system.
 From the network layer we use the IDS/IPS and firewall to filter out the packets
as we desire on the system.
Architecture Explained
 The Vehicle is connected via the WIFI and is constantly connected
on the mobile network.
 The data that is collected by the vehicle to infrastructure like traffic
signals, etc or near by vehicles are constantly relied to the gateway
for the further processing.
 The Vehicle communicates to the gateway via the secure WAP3
protocol.
 It goes through the DNS connected via the internet and reaches the
DMZ to route to the gateway.
 The gateway interprets the message from device and converts into
the consumable format by the cloud deployed service application.
 The converted/transformed message is relayed via the messaging
queues
Architecture Explained - Continued
 The queue messages are relayed to the cloud deployed applications and the
appropriate processing is done for the received messages.
 A notification system is enabled to send and receive any of the SOS message
between the Vehicle and the backend systems.
 The services deployed on the Kubernetes cluster shall communicate securely
via the mTLS protocol. This ensures that if one of the service is compromised, the
whole system is not compromised.
 Thus, the above architecture describes the end to end follow in the security
perspective.
 The solution communicates to the infrastructure via the sensors/cameras. It
controls the steering wheel, brakes and speed based out of the signals and the
position of the near by vehicles. This is taken care at the Vehicle level and the
appropriate software management for the vehicle control is installed on the
vehicle.
Assumptions / Challenges
There are various challenges/tradeoff’s that comes along with the proposed
architecture.

 Security and Privacy Concerns:

Data Privacy: V2X systems collect and transmit vast amounts of sensitive data,
including vehicle location, speed, and driver behavior. Protecting this data from
unauthorized access and misuse is paramount.

Cybersecurity Threats: V2X systems are vulnerable to cyberattacks, such as hacking


and spoofing, which could compromise vehicle safety and control.

Authentication and Authorization: Ensuring the authenticity and trustworthiness of


communication between vehicles and infrastructure is crucial to prevent malicious
attacks.
Assumptions / Challenges - Continued
 Communication Reliability and Latency:
Reliable Communication: V2X systems must ensure reliable communication in
diverse environments, including urban and rural areas, with varying levels of
interference and signal strength.
Low Latency: Real-time communication is essential for safety-critical applications
like collision avoidance and emergency braking. Low latency is crucial to enable
quick responses to dynamic traffic conditions.
 Standardization and Interoperability:
Standardization: Developing and adopting common standards for V2X
communication protocols and data formats is essential to ensure interoperability
between different vehicle manufacturers and infrastructure providers.
Interoperability: Ensuring seamless communication between vehicles from
different manufacturers and with various infrastructure components is crucial for
widespread V2X deployment.
Assumptions / Challenges - Continued

 Scalability and Cost-Effectiveness:

Scalability: V2X systems must be scalable to accommodate the increasing number


of connected vehicles and infrastructure components.

Cost-Effectiveness: Implementing V2X technology on a large scale requires cost-


effective solutions for both hardware and software components.

 Legal and Regulatory Framework:

Liability: Defining liability in case of accidents involving V2X-enabled vehicles is a


complex legal challenge.

Regulatory Framework: Developing clear and comprehensive regulations to


govern V2X deployment and operation is essential to ensure public safety and trust.
Conclusion
 Overcoming these challenges requires collaboration between automotive

manufacturers, technology providers, telecommunications companies,

government agencies, and other stakeholders. By addressing these issues

proactively, we can pave the way for a safer, more efficient, and sustainable

transportation future.
Thank You

You might also like