{"id":25527,"date":"2020-03-22T01:20:51","date_gmt":"2020-03-22T01:20:51","guid":{"rendered":"https:\/\/www.eccu.edu\/?p=25527"},"modified":"2024-04-22T07:07:00","modified_gmt":"2024-04-22T07:07:00","slug":"why-a-pentesting-report-is-extremely-important","status":"publish","type":"post","link":"https:\/\/www.eccouncil.org\/cybersecurity-exchange\/cyber-talks\/why-a-pentesting-report-is-extremely-important\/","title":{"rendered":"Why a Pentesting Report is extremely important"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

\"Tim<\/p>\n

Speaker<\/strong> Tim Chase,
\nDesignation:<\/strong> Director of Field Security at Collibra
\nTopic:<\/strong> Why a Pentesting Report is extremely important
\nDate of Webinar:<\/strong> 29th<\/sup> June, 2020
\nTime and Location:<\/strong> 10:00 am CST\/ 8:30pm IST\/ 4:00pm GMT<\/p>\n

Watch Now<\/a>
\n
<\/strong><\/p>


<\/strong><\/p>


<\/strong><\/p>

Speaker Bio:<\/strong>
\nTim Chase has been working in information security for 15 years in many different roles including leading security teams focusing on cloud, appsec, and overseeing Security for a leading healthcare training company. Over the last few years, he has been focusing his efforts on DevSecOps and the intersection of AppSec, DevOps, and Cloud. He has presented at multiple conferences on this topic in including RSA and ISSA InfoSec. In addition he is a LinkedIn Training author where he has training to help build DevSecOps into the development pipeline. He currently works at Collibra, a data intelligence company, where he runs the Field Security organization working to educate clients and prospective clients on the security of the Collibra Platform.<\/p>\n

Topic Abstract: <\/strong>
\nAll penetration tests provide a detailed report of the entire process, including a list of vulnerabilities, based on severity, and solutions to help secure the organization.<\/p>\n

In this webinar, we will understand the business impact of a penetration testing report, the basic measures to be taken for better security, and how a report should be read and formulated.<\/p>\n

Key Takeaways: <\/strong><\/p>\n

    \n
  1. How report writing reflects technological shortfalls and measures to be taken.<\/li>\n
  2. How frequently penetration tests are required.<\/li>\n
  3. The repercussions of vulnerabilities not being fixed.<\/li>\n<\/ol>\n

    *Examples, analysis, views and opinion shared by the speakers are personal and not endorsed by EC-Council or their respective employer(s)<\/p>\n

    <\/a>
    \n