Implement Custom Error Response Pages #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements customizable error pages that appear to contain sensitive system information to keep attackers engaged longer. The error pages serve as honeytokens, encouraging attackers to spend more time investigating, which allows for better intelligence gathering about their techniques and intentions.
Changes Made
Created a modular error handling system with the following components:
Added features to make error pages appear to contain sensitive information:
How to Test
Start the Flask logging server:
python -m flask_logging_server.logserver
Screenshots
http://localhost:5000/trigger-error/401

http://localhost:5000/trigger-error/403

http://localhost:5000/trigger-error/404

http://localhost:5000/trigger-error/500

http://localhost:5000/trigger-error/503

Related Issue
Closes #42 - Custom Error Response Pages
@gtheodoridis