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: | Inspecting Code for Security |
|---|---|
| Date: | Mon, 20 Sep 2004 15:55:35 -0400 |
I have a background in programming and code inspection. However our inspections were not targeted at security, instead they looked for logic errors, over complex code, missing comments, etc. With security in mind what things other things should I be looking for in a code inspection? I can think of the following, but I'm sure there are others: - buffers that could be overflowed - ensuring all input is validated (checked to ensure it is of the proper type & format) - ensuring passwords & other encrypted date is not stored unencrypted in memory - ensuring strong encryption is used - ensuring no easter eggs / backdoors are left in the code - ??? Thanks
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Learning WAN technologies, Mark Teicher |
|---|---|
| Next by Date: | RE: Password Protection, Bowes, Ronald (EST) |
| Previous by Thread: | Laptop Encryption & Hibernation, James McGee |
| Next by Thread: | Re: Inspecting Code for Security, George V. Neville-Neil |
| Indexes: | [Date] [Thread] [Top] [All Lists] |