It's important to address security concerns that are often overlooked in any REST API development. This issue aims to implement security layers to protect the application and its data from unauthorized access.
NOTE ⚠️: Currently, the Car Services REST API is not deployed on a public server, so this issue will apply to the DEV environment only. However, when the app is deployed on a server, having proper protection will be essential. Also, while this project is a sample and not intended for storing real data, implementing security layers is crucial. It provides a practical example of how to configure security in real-world projects.
Examples of potentials threats against APIs :
Unauthorized access: Anyone can use the API without restrictions.
Stolen data: Sensitive data can be accessed, modified or stolen by attackers.
DoS Attacks: The API could be overwhelmed by malicious requests.
Documentation
After implementing the security layers, please document the configuration and explain the steps taken. This will help others learn how to apply similar security measures in their own projects.
It's important to address security concerns that are often overlooked in any REST API development. This issue aims to implement security layers to protect the application and its data from unauthorized access.
NOTE ⚠️: Currently, the Car Services REST API is not deployed on a public server, so this issue will apply to the DEV environment only. However, when the app is deployed on a server, having proper protection will be essential. Also, while this project is a sample and not intended for storing real data, implementing security layers is crucial. It provides a practical example of how to configure security in real-world projects.
Examples of potentials threats against APIs :
Documentation
After implementing the security layers, please document the configuration and explain the steps taken. This will help others learn how to apply similar security measures in their own projects.