SHARE



ABOUT THE AUTHOR


Gary Audin
Gary Audin is the President of Delphi, Inc. He has more than 40 years of computer, communications and security...
Read Full Bio >>
SHARE



Gary Audin | August 23, 2012 |

 
   

New NIST Computer Security Guide Published

New NIST Computer Security Guide Published A major focus of the guide is a step-by-step set of instructions on how to create and operate an incident response team.

A major focus of the guide is a step-by-step set of instructions on how to create and operate an incident response team.

Good advice can be hard to find. IT security is continuously a subject of blogs, articles, and white papers, many written by or for a vendor. The National Institute of Standards and Technology (NIST) has produced its own new publication, the "Computer Security Incident Handling Guide". This vendor-neutral guide sells no products, does not limit its discussion to just one issue but covers many, and is a reference for the future. It is not a guide to read overnight, but a 79-page book for those dealing with IT security. Most of the recommendations are just as valid for communications security.

A major focus of the guide is a step-by-step set of instructions on how to create and operate an incident response team. This is very important because there appears to be no end of security attacks and data breaches. The enterprise must be ready to document, analyze and track down the attack to resolve it and prevent its reccurrence.

The guide has a series of recommendations valid for government, business and academic institutions:

* Create an incident plan and policy for the organization including on-premises and cloud-based services.

* Incident response and reporting procedures should be developed and followed; this should not just be a paper plan.

* Set guidelines for communicating with every possible organization, internal such as the legal department and external such as law enforcement agencies.

* Determine the incident response team structure and the qualifications necessary to be a member of the team staff

* The services that the incident response team should provide and to whom must be established.

* Don't forget that the incident response team needs training, not just once but ongoing.

One point that was made in the guide is that it is less costly to prevent a security incident than to resolve one. Security breaches not only cost the enterprise, they may damage their reputation and eventually their customer base. The goal of the incident response team is to reduce the number of incidents in the future.

Documentation of the incident and its resolution are very important. This information should be used to build better protection. This information should be shared with interested organizations such as law enforcement agencies, service providers, and vendors. The parties that should share in the documentation should be determined in advance, not after an incident occurs.

The guide offers a list of attack vectors--methods used in security breaches--for which procedures should be in place for prevention and remediation. Some examples of attack vectors:

* An attack can be executed by inserting removable media such external disk drives, flash drives, and CDs.

* An attack may use brute force methods to degrade, destroy or compromise a network or systems--this is called attrition.

* Web based attacks are all too common.

* An attack can be part of an e-mail message or attachment.

* Organizations have developed and published security policies and procedures. Attacks can occur when these are not followed or enforced.

* When equipment is lost or stolen, it can be used as an attack tool.

The guide also provides three other guidelines.

1. "Organizations should emphasize the importance of incident detection and analysis throughout the organization". This should come from the top of the organization, not from the bottom.

2. "Organizations should create written guidelines for prioritizing incidents." This is important since there will always be limited resources and time to respond to an incident.

3. "Organizations should use the lessons-learned process to gain value from incidents." If a similar attack has already been resolved, then it should be possible to resolve another attack of the same kind faster with less staff effort.

A final recommendation is that an attacked organization should reach out to other trusted organizations that may be able to provide valuable information and insight to the problem and its resolution.

The schematic below shows how the Incident Response Team may be composed.





COMMENTS



August 16, 2017

Contact centers have long been at the leading edge of innovation in communications technology, given their promise of measurable ROI and the continual need to optimize customer interactions and sta

July 12, 2017

Enterprises have been migrating Unified Communications & Collaboration applications to datacenters - private clouds - for the past few years. With this move comes the opportunity to leverage da

May 31, 2017

In the days of old, people in suits used to meet at a boardroom table to update each other on their work. Including a remote colleague meant setting a conference phone on the table for in-person pa

August 16, 2017
World Vision U.S. is finding lots of goodness in RingCentral's cloud communications service, but as Randy Boyd, infrastructure architect at the global humanitarian nonprofit, tells us, he and his team....
August 11, 2017
Alicia Gee, director of unified communications at Sutter Physician Services, oversees the technical team supporting a 1,000-agent contact center running on Genesys PureConnect. She catches us up on th....
August 4, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, has lately been working on integrating enterprise communications into Internet of Things ecosystems. He shares examples and off....
July 27, 2017
Industry watcher Elka Popova, a Frost & Sullivan program director, shares her perspective on this acquisition, discussing Mitel's market positioning, why the move makes sense, and more.
July 14, 2017
Lantre Barr, founder and CEO of Blacc Spot Media, urges any enterprise that's been on the fence about integrating real-time communications into business workflows to jump off and get started. Tune and....
June 28, 2017
Communications expert Tsahi Levent-Levi, author of the popular BlogGeek.me blog, keeps a running tally and comprehensive overview of communications platform-as-a-service offerings in his "Choosing a W....
June 9, 2017
If you think telecom expense management applies to nothing more than business phone lines, think again. Hyoun Park, founder and principal investigator with technology advisory Amalgam Insights, tells ....
June 2, 2017
Enterprises strategizing on mobility today, including for internal collaboration, don't have the luxury of learning as they go. Tony Rizzo, enterprise mobility specialist with Blue Hill Research, expl....
May 24, 2017
Mark Winther, head of IDC's global telecom consulting practice, gives us his take on how CPaaS providers evolve beyond the basic building blocks and address maturing enterprise needs.
May 18, 2017
Diane Myers, senior research director at IHS Markit, walks us through her 2017 UC-as-a-service report... and shares what might be to come in 2018.
April 28, 2017
Change isn't easy, but it is necessary. Tune in for advice and perspective from Zeus Kerravala, co-author of a "Digital Transformation for Dummies" special edition.
April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.