Let us continue with Web application protesting in this lecture.
We will see how to prevent Web server attack.
I have listed down some of the key bullet points of the personal attacks on your screen.
So the first is, please, Web servers in separate secure server security segment on the network.
And I will be posting Network ByDesign with at least three segments, namely in the next segment.
Secure Server Security segment often called Calls Demilitarized Zone is the DMZ and Internal Network,
please.
The Web server.
Instead of our security segment, it is the DMZ of the network isolated from public network as well
as the internal network.
Firewalls should be placed for internal networks as well as internal traffic going towards DMZ next
to the patches and updates scan for existing vulnerabilities in the patches and update the server software
regularly before applying any service back.
Hotfix the security patch here and peer review all the relevant documentation.
Test the service packs and hotfix unrepresented to non production environment prior to being deployed
to the production.
Ensure the server outages are scheduled and a complete set of backup tapes and emergency repair risks
are available.
Have a backup plan that allows the system and enterprise to run to their original state prior to the
full implementation.
The next is check for Portal Block, all unnecessary reports Internet control, message protocol, traffic
that is the ICMP traffic and unnecessary protocol such as net bios and SMB.
Hard on the D.C. baby stack and consistently apply the latest software patches and updates to system
software if using insecure protocols suspended three SMTP FPP take appropriate measures to provide secure
authentication and communication, for example, by using IP policies.
If remote access is needed, make sure that the remote connection is secured properly by using Penlington
encryption protocols, the next account settings remove all unused modules and applications extensions,
disable unused default user accounts created during the installation of an operating system for creating
a new web directly.
Grant the appropriate rate is the least possible NTFS.
Since the anonymous user being used from the IRS web server to access the web content, you secure the
permissions, NTFS permissions and dot net framework's access control mechanisms, including your authentication.
Slow down brute force and extra attacks with strong password policies and then audit and be alert for
login failures.
I don't process using the least privileged accounts as well as least privileged services and user accounts.
The next is detecting Web server hacking at the use of a detection system to detect hacking attempts
on the Web server Web site.
Change detection system involves running specific script on the server that detects any changes made
in the existing executable for a new included file on the server, periodically comparing the hash values
of the files on the Web server with the respective must but hash value to detect the changes made in
the codebase, alerting the user upon any detection on the server.
For example, we observe, is the script that goes through your entire folder and detects any changes
made to your code and alerts you using the email.
So how different is that?
Good audit reports on the server regularly to ensure that an insecure or unnecessary service is not
acting on your web server.
Ensure that the cert data ranges are valid and the certificates are used for their intended purposes.
Ensure that any certificate has not been revoked and certificates public is valid all the way to a trusted
route.
Authority ensure that the protected resources are mapped, its GDP for handler and unused modules are
removed.
Implement secure coding practices, district code access security policy settings, apply restricted
Ishmael's and block remote registry administration secure the same standalone servers only ensure that
the security settings are configured properly and access to the Mbox file is restricted with hardened
NTFS permissions and a last screen and filter the incoming traffic requests.
In the next lecture, we will see different Web application servers like Zamp, Wempe Lamp and many
more.