Project Two Milesone 1 Blackstone
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
400
Subject
Information Systems
Date
Apr 3, 2024
Type
docx
Pages
3
Uploaded by ABusch18
My approach to presenting the findings to an audience would be, primarily, to focus on keeping it simple, quick, and interesting. Meetings and presentations are frustrating enough to attend, they do not need to be boring, too. To do this, I would utilize a PowerPoint presentation and speak directly to the audience in a calm, personable fashion. Theoretically, I should know the individuals I am speaking to or, at least, will be working with them in some fashion. As a result, my tone should be friendly and welcoming. There are many strategies I would utilize to simplify technical jargon to a non-technical audience. As stated above, I should know my audience and plan my presentation accordingly. Using common terms for more technical phrasing would be the first step. The audience doesn’t need to know the specific terminology for every vulnerability found, nor will they understand them. Hearing “NVT Microsoft…” and a bunch of numbers over and over will make even the most technologically savvy person stop paying attention. Simplifying the vulnerabilities down to what they are, not their classifications or complex names will make everyone pay more attention.
Referring to the vulnerabilities by what problems they cause would be another method of simplifying the presentation. Instead of repeating “NVT: SMB Brute Force Logins With Default Credentials” over and over, simply referring to this vulnerability as “compromised logins” or similar would get the point across. Likewise, there is no need to list off every login that has been compromised. The people responsible for remediation have a list, we do not need to waste time by announcing them all.
Additionally, paying attention to the audience to clarify things should they look confused or lost. Answering some questions during the presentation is acceptable, provided they are not answered later or would take too long to get into at the time. But redirecting the question to relevant information or offering to follow up afterwards is easily done.
My visual aid would be simplistic. It would offer bullet points on each slide, with most of the information being provided by the speaker. Any images or animations I included would be minimal. The background and text would be legible and simple. I would avoid unnecessary clip art or distracting backgrounds on the slides. The vulnerability’s actual terminology and a brief explanation of what that means will likely be present, as well as how to resolve the issue and which category it should be under. Keeping it simple would leave more room for verbal explanations and utilize the visual aid as just that: An aid. It would allow the speaker to reference specifics and, should it be needed, provide the audience with spelling or phrasing to write things down. I would also like to include a rough timeline of when we can expect to have vulnerabilities taken care of. This would eliminate questions about expectations of when it is to be finished. The basic information I would make sure is included in the presentation would be the categories of vulnerabilities, the specifics of those vulnerabilities (albeit simplified in explanation,) and the expectations and process for remediation. The presentation should relay what we learned, what that means and how we intend to solve it. As well as establishing how we will prevent it from happening again and what remediation looks like. Potential policy updates should be included as well. This will provide the audience with fair warning of changes that might be coming and simultaneously offer explanation on why these policies are being changed. The presentation should end with answering any questions the audience might have and explaining anything they want more details on. This would also be an ideal time to point out any
issues we have already resolved and any future policy updates we should be expecting to come down the pipeline. References:
How to explain technical ideas to a non-technical audience
. (2020, February 6). @LucidSoftware. https://www.lucidchart.com/blog/how-to-explain-technical-ideas-to-a-
non-technical-audience
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help