im Higher College is a fictional entity that you will use to consider threats and recommended responses. Following are some important contextual details:

Aim Higher College has deployed an open source blog package. This package uses a database backend and allows users to create user IDs, sites, and their own content to post on it$.$ Recently, the service has had off$-$campus users who have posted links that appear to be directed towards university resources, but they are being redirected toward off$-$campus malware sites. What would you recommend that the application administrator should do$?$

A developer for Aim Higher College is creating a web server form for submission of calendar events to the College$$s event calendar. What protective measures would you suggest ensuring its security?

Database administrators from Aim Higher College$$s central information technology $($IT$)$ group have contacted the security team noting that they are finding odd entries in a web application$$s backend database. Some of the entries appear to be SQL commands such as $$UNION$$ and $$JOIN$,$ which cause them to think that an attacker is probing the web application. What recommendations would you provide to protect both the application and the back$-$end database?

A scan of Aim Higher College$$s primary web server from using a Nikto shows a large number of default configuration files and sample files on many of the older servers. What is wrong with this, and what should be done about it$?$ Why are having default configurations left as default a danger to the security of the web server? For each of the scenarios described in the Background Information section above, explain what the threat or threats are, what defenses you would recommend, and why.