SEC504: Hacker Tools, Techniques, and Incident Handling

Experience SANS training through course previews.
Learn MoreLet us help.
Contact usBecome a member for instant access to our free resources.
Sign UpWe're here to help.
Contact UsIt is inevitable that vulnerabilities will be discovered in the production of information technology products, regardless of how much time and effort is placed into identifying and removing flaws during initial development. Based on this inevitability one would surmise that a logical structured procedure would be followed for disclosing newly discovered vulnerabilities. However the current process for disclosing vulnerabilities can range from a loosely organized effort to utter chaos. This lack of structure has caused the eruption of a heated debate within the information security community. This debate has been going on for almost a decade. Yet to date there is no formal, accepted, and enforced standard of practice. Each side in this debate has expressed valid concerns both for and against the various concepts of disclosure. As a result this vigorous debate has given rise to the new term 'Responsible Disclosure'. Within this document I will attempt to define 'Responsible Disclosure'. I will briefly explore some key events in vulnerability disclosure. I will also attempt to explain the conceptual differences between full disclosure nondisclosure limited disclosure and responsible disclosure. Finally I will examine some existing disclosure policies and proposed standards.