@manikanthar1295 By configuring Sling, Adobe Dispatcher, a web application firewall, installing the latest security hotfixes and implementing a protected network environment - we can protect from DOS attack.
Use the mod_rewrite module to perform URL validations (if the URL pattern rules are not too complex).
Prevent the dispatcher from caching URLs with spurious extensions by using filters.
For example, change the caching rules to limit caching to the expected mime types, such as:
- .html/.jpg/.gif/.swf/.js/.doc/.pdf/.ppt
To safely enable full functionality on the publish instances, configure filters to prevent access to the following nodes:
Then, configure filters to allow access to the following node paths:
/etc/designs/*
/etc/clientlibs/*
/etc/segmentation.segment.js
/libs/cq/personalization/components/clickstreamcloud/content/config.json
/libs/wcm/stats/tracker.js
/libs/cq/personalization/* (JS, CSS and JSON)
/libs/cq/security/userinfo.json (CQ user information)
/libs/granite/security/currentuser.json (data must not be cached)
/libs/cq/i18n/* (Internalization)
Validate all these changes in lower environment before before implementing in Production.
Reference link : https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/security-checklist.html
https://aemexperts.blogspot.com/2019/03/how-to-prevent-dos-attacks-in-aem.html
Regards,
Raja