full-disclosure - Hosting Provider Refuses to Share Server Logs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue Aug  2 14:50:42 2005
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: Hosting Provider Refuses to Share Server Logs -
	How to	Proceed?

> I've never dealt with an intrusion before, but I am the tech for the

That's all you need to say.

The server logs probably won't tell you exactly what happened, and it 
doesn't matter anyway. ANYTIME you have a hack, regardless of how 
trivial, you rebuild from scratch.

Why? Because you'll never know what was left behind. I've been doing 
post-mortum analysis of hacked boxes for years, and I still don't trust 
my own abilities to find everything -- thus they all get rebuilt 
offline, and nothing that's executable (directly or otherwise), and no 
config files get restored.

More specifics on the exact config, and we can give links on how to 
secure the next install (eg: what httpd, what O/S, etc.).

Cheers,

Michael Holstein CISSP GCIA
Cleveland State University