You know the time of the posting from the proxies access log (see my previous post). You can read the forum thread. Each post has a time associated with it. Therefore you can work out which post is theirs.
You know the time of the posting from the proxies access log (see my previous post). You can read the forum thread. Each post has a time associated with it. Therefore you can work out which post is theirs.
But you still don't get PMs and there are things where they are likely to confide in one or two people they know from the board. We already know their user names so we can monitor their postings with ease.
That's not a big deal either. It's just a case of cross referencing the url with the squid store.log and pulling the relevant items from the on disk cache.
I have to agree with Geoff on this.
Yes we all want to ensure that those at risk are monitored and reported to the correct teams but at a cost of 3, 4 or 5k is way to high when you can do it for free with the tools you most likely have already.
Yes Securus does some ofthe work for you but you still have to go through the logs to get, the screenshots, you need.
I currently use 3 layers of content filtering DansGuardian, ISA 2004, and a Bloxx appliance all of which give me all the information I need when I cross refernece the custom logon database I have for students logon/logoof activity.
This allows me to pinpoint and confirm exactly who accessed what, from where and when.
OK so i don't have a screenshot to go with it but the proof is there, and anyway just becouse you have a screenshot does not mean anything more than if you don't, students will always claim that someone used thier logon details to try and get out of it.
There are currently 1 users browsing this thread. (0 members and 1 guests)