A small browser tool for reviewing sample server and sign-in logs. It highlights repeated failures, suspicious paths, privilege-related wording, and repeated source IPs, then turns the matches into a simple risk summary.
I built this as a beginner blue-team project because log review is one of the first practical skills in security work: read the evidence, group the activity, and explain what looks unusual.
Open index.html in a browser.
npm testThe test checks JavaScript syntax, required project files, README sections, screenshot presence, and old template/security placeholder wording.
- Accepts pasted or uploaded
.txtand.logfiles. - Uses clear rule-based checks instead of hidden scoring.
- Groups findings by source IP where possible.
- Shows matched evidence and response notes.
- Shows a short analyst checklist after each run.
- Exports a JSON report for later review.
This is complete as a beginner browser-based blue-team project. It has a sample log, visible scoring, response notes, export, screenshot, and a smoke test.
Use sample logs or logs you are allowed to review. Do not upload real customer, school, or workplace logs unless they have been cleaned first.
- Small detection rules are easier to trust when the matched evidence is shown beside the result.
- A log tool is more useful when it explains why something was flagged, not just that it was flagged.
- Even a simple browser app needs tidy sample data to feel finished.
- Add a few more sample logs for failed sign-ins, web probes, and normal traffic.
- Add highlighted evidence inside the pasted log text.
- Add rule toggles for comparing different detection ideas.
I added a short portfolio note for the defensive log-analysis workflow in docs/portfolio-notes.md.
