About Us | Contact Us
View Cart

Broadcast Awareness

By Dan Hadaway | Monday, September 18, 2017 - Leave a Comment

Steps One and Two . . .


How to Substantially Decrease (and Streamline) Response Time
Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . .


ServIcons_ITAudit_01

Given that we have been watching networks since 2000, we have seen a LOT of incident responses.  There is a small, seemingly minor sub-process to incident response, that we have noticed makes the response go much better.  We have found that the Incident Response Team is in a good position to turn lemons to lemonade when an appropriate, streamlined, quick initial response is automatic.

The sub-process present in each of the successful responses we’ve seen over the years was so noticeable that we named it . . . Broadcast Awareness . . . and added a description of it in both our Acceptable Use Policy and our Incident Response Program templates.   Acceptable Use because you want every employee who handles information to understand it.  Incident Response because you want your Incident Response Team to rely upon it as a “control.”

“Because our team knew to broadcast awareness, thanks to your pretext calling tests, we were able to shut down that wire transfer fraud.  It saved us hundreds of thousands of dollars!”

– Bank President who originally didn’t like the finding.

Over the years . . . again, of watching businesses respond to technology incidents . . . we have come to believe in Broadcast Awareness so much that we have added it to our audit checklists, even though . . . as the president of the bank quoted above pointed out . . . there is no guidance requiring it.

So what do we mean by Broadcast Awareness?

“Broadcast Awareness” is the first two steps that all users should be trained to execute whenever they become suspicious about either technology or information.

  1. Contain the Incident.
  2. Inform the Appropriate Everybody.

You’d think the above two steps would “go without saying,” which is also what the above-quoted bank president pointed out.  Sure, it should go without saying.

But when we watch businesses miss their opportunity to turn lemons to lemonade, it is because we see the first encounter send an email to his or her Information Security Officer, and then go back to work.  It’s because we see the entire team create a whole bunch of activity around the fact that there is a virus on a workstation, but nobody thinks to disconnect the workstation from the network.  It’s because time after time we continue our pretext calling tests, or our physical breach tests, for weeks after the first suspicious “shut-down,” and nobody else in the institution is aware of our attack attempts.

Broadcast Awareness is a valuable process to teach.  It only takes up an additional 101 words in your Acceptable Use Policy, if you add it.  Here’s typical policy language:

Reporting Suspicious Activity and/or Suspected Security Incidents

In the event that you notice activities by other employees, vendors, or customers or you become aware of security incidents, weaknesses, and software malfunctions, or are concerned there may be a virus on your computer, please contain the event by disconnecting your workstation from all networks if possible, then report such suspicions to your immediate supervisor who will help you “broadcast awareness,” meaning that you will inform all appropriate persons so that they will not “fall victim” to the suspicious activity. After broadcast awareness, in the Information Security Officer.

Notice that the above language requires the notice of the “appropriate everybody,” AND THEN notification of the Information Security Officer.  This is essential.  So many incidents are exacerbated because an employee simply emails the ISO and returns to work.  The incident goes un-contained and others fall victim to the incident.

When providing awareness training to users, we go so far as to use the following graphic to illustrate the process:

The reason we find this useful is that if users are aware of what happens after the incident is contained and handed off to the ISO, the overall incident response process proceeds smoother.  In other words, knowing that the ISO may call an emergency incident response team meeting gives a branch manager a sense of what is going to happen.

To summarize:  if you want to grease the machinery of incident response, teach your employees Broadcast Awareness!


Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex

Dan’s New Leaf is a fun blog to inspire thought in the area of IT Governance.”

 


same_strip_012513


 

Latest News
    Our Lead Non-Technical Auditor takes a look at the new AIO Guidance… Architecture, Infrastructure, and Operations (AIO) is the latest booklet released by the Federal Financial Institutions Examination Council (FFIEC) in their line of  IT Examination Handbooks. It is an update to their 2004 Operations booklet and, as the name implies, expands into the areas […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Many organizations still fail to consider the unique risks posed by cloud computing… An article review. Last month thousands of Western Digital MyCloud device owners learned about the risks of cloud-based solutions the hard way: their data had been wiped remotely due to a flaw in the internet-facing component of their external hard drives. While […]
    infotex does not use Kaseya… We are protecting our Clients! Another blog post meant to inspire thought about IT Governance . . . . To all infotex managed security service Clients: As you may be aware there was a large ransomware attack recently that leveraged a remote management tool called Kaseya that is used by many […]
    While we’re not a news service, we often use current events to comment on trends and our services. This blog is intended to get people thinking about topics and trends in Technology Risk Management, through our article reviews, as well as through original blog articles about current events and our MSSP services (such as our […]
    PRESS RELEASE – FOR IMMEDIATE RELEASE BUSINESS NEWS Dan Hadaway and Sara Fultz co-wrote an article in the Spring 2021 issue of the Ohio Record, the Official Magazine of the Ohio Bankers League.  Find out on page 20 and 21 of the magazine how tabletop testing strengthens bank cybersecurity. You can read the article here! […]
    You’ve heard it from every MSSP you’ve met: the definition of a SIEM is in the eye of the beholder. But at infotex, we are not talking about the database – an asset whose definition is continuously evolving. We’re talking about the way three teams collaborate in an overall Technology Risk Monitoring process. And whether […]
    After the large number of high-profile breaches in the recent months, it is easy to become disconcerted about how to prevent such things from happening to your Bank. The answer to preventing a breach is a very complex one. infotex will explore this with you! The heightened level of awareness and extra protective tendencies that […]
    A follow-up on Dan’s 2008 Password Manifesto On the NIST Publication on Digital Identity Guidelines Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . In June 2017, NIST released a special publication on digital identity, NIST SP 800-63, that is starting to get the attention […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]