Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Assessment Methodology |
|---|---|
| Date: | Tue, 26 Oct 2004 21:38:27 -0500 |
I've used OCTAVE as a base and just modified it to what I was reporting. Keeping right on the suggested guidelines gets a bit wordy and looses its audience pretty quick. It's a good base to work from though. -----Original Message----- From: robert@dyadsecurity.com [mailto:robert@dyadsecurity.com] Sent: Monday, October 25, 2004 6:58 PM To: Paul Ryan Cc: security-basics@securityfocus.com Subject: Re: Assessment Methodology Paul Ryan(pryan@rogers.wave.ca)@Mon, Oct 25, 2004 at 02:40:53PM -0400:
I am in the process of doing an audit on various portions of our IT infrastructure. I wanted to know everyone's opinions on what the preferred metric system is. I've been researching OCTAVE - my objective is to
provide
a report with a scheme that easily reflects the status based on our
current
policy. Something like pass,fail or compliance % - just brainstorming here
We've always done tests based on what we can actually measure. We try to represent findings in terms that clearly articulate what we measured. As far as methodologies that we've seen, evaluated, and used, I have had the best practical results by using the Open Source Security Testing Methodology Manual (www.OSSTMM.org) from the Institute for Security and Open Methodologies (www.ISECOM.org). Robert -- Robert E. Lee CTO, Dyad Security, Inc. W - http://www.dyadsecurity.com E - robert@dyadsecurity.com M - (949) 394-2033
smime.p7s
Description: S/MIME cryptographic signature
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: IIS Logfile, Andrew Shore |
|---|---|
| Next by Date: | Re: Is this normal?, Barrie Dempster |
| Previous by Thread: | Re: Assessment Methodology, robert |
| Next by Thread: | IIS Logfile, mfernandez |
| Indexes: | [Date] [Thread] [Top] [All Lists] |