PLEASE SEE ATTACHMENT!!
Project Submission Steps
You are a Security Analyst for a toll road authority (TRA) in a major city. The TRA is about to undergo its yearly IT audit, and you have been asked to make sure everything goes well and that there are no audit findings.
The TRA has eight toll road plazas with multiple lanes. Three lanes are for vehicles with prepaid toll tags. The other three are for drivers paying in cash. In addition, there are several on ramps and off ramps with toll tag sensors that automatically debit the customer’s account when the vehicle passes through.
All toll plazas and ramps are equipped with cameras that record vehicles passing through them. They also take pictures of each vehicle’s license plate in case the driver does not have a toll tag. The pictures are then examined by advanced imaging software that determines the plate number, identifies the name and address of the driver associated with that vehicle, and sends a bill to that address notifying the driver of the charge, along with instructions on how to pay it (this is a drastic oversimplification of how the toll violations process actually works, but for the purpose of this project it will suffice).
1. Using a graphical program of your choice, create a flowchart or diagram of how the system is architected based on the information given.
a. LucidChart and Draw.io are two free flowcharting options that should suffice.
2. Assume there are firewalls protecting the network perimeter and that only port 443 is being allowed to the web servers. Also assume that the web servers are located in a DMZ, the WebLogic servers are on the internal network, and
WebLogic server connections come only from proxied web server requests.
NOTE: The toll violation process is NOT in scope for this exercise.
3. Creating a test plan to assess the following:
● Web site security. There are some concerns about some of the fields not being properly coded.
● WebLogic servers. One of the servers was the victim of a “coinminer attack” last year due to an unpatched vulnerability. This attack impacted the availability of the server by causing the CPU utilization to spike past 70%There is tremendous concern, therefore, around the effectiveness of the patch management process. In addition, some WebLogic Server configuration data (and some of the applications, including JSP and HTML pages guarded with WebLogic Server acls) are stored in clear text on the file system. A user or intruder with read access to files and directories can easily defeat any application security established with WebLogic Server authentication and authorization.
PLEASE SEE ATTACHMENT!!