Risk
3/6/2012
12:25 PM
Connect Directly
RSS
E-Mail
50%
50%

5 Steps To Stronger SMB Application Security

How one never-breached, midmarket retailer avoids the too-small-to-be-secure mindset in favor of Fortune 500-grade threat prevention.

9 Startups To Watch In 2012
9 Startups To Watch In 2012
(click image for larger view and for slideshow)
Small and midsize businesses (SMBs) have a litany of excuses at their disposal for spotty security practices, with slim budgets and IT departments leading the list. Those two, in particular, are valid reasons. You can either cave to them, or secure your company's assets anyway.

Bob's Stores chose the latter for its approach to application security. The midsize, regional retail chain employs roughly 650 people; suffice it to say the lion's share of the staff works on something other than application security.

"IT is very light," said Yaron Baitch, director of IT and information security at Bob's Stores. In an interview, Baitch outlined how Bob's Stores ensures top-notch security for both its internal employee and external customer applications, in spite of limited resources.

[ The new Internet protocol is coming--are you ready? See 3 Ways For SMBs To Plug IPv6 Security Holes. ]

He shared a panel on the topic last week at the RSA Security Conference. It's a fairly straightforward recipe grounded in an organizational understanding that the company's bottom-line health is at stake. And it works: Bob's Stores has never had a breach. Baitch half-jokes that acknowledging this fact makes his company a juicier target for hackers. Dark humor aside, that speaks to a basic security mistake many SMBs still make: Thinking no one would bother with their "small" business.

Here's how Bob's Stores sidesteps that myth in favor of secure applications.

1. Security Is A State Of Mind
That basic level of awareness is a must--not just for IT, but for each and every person in the organization, regardless of their job description. This is the step that sounds easy, yet gets bypassed on a regular basis. "Security is everybody's responsibility," Baitch said. That mindset should extend to vendor-built applications, too; Baitch points out that if there's a security breach, your customers will associate it with your brand, not with a backend developer. "Making sure everyone's playing on the same page is critical," Baitch said.

2. Let Your Pain Points Make Your Business Case
Baitch considers it good fortune that his company must adhere to Payment Card Industry (PCI) standards. I'll repeat that: Baitch is glad he has to deal with PCI, even though he doesn't have the compliance budget of much larger retailers that operate under the exact same rules. He's not insane; he's pragmatic. PCI essentially makes Baitch's business case for him when he explains the importance of security to executives and other stakeholders. If your company contends with heavy compliance burdens, use those to prove your security case to the rest of the business. Still, Baitch acknowledges it's not always easy. Negotiation with the business is key--if you aren't so "fortunate" to deal with a regulatory quagmire, come up with a different set of reasons and priorities that non-technical people can understand and buy into.

3. Know Your Strengths And Weaknesses
Don't shy away from your natural limits. You don't have Google's gazillions; you can't spend your way past every business challenge. Boo-hoo: Double-down on your strengths and shine an equal spotlight on the skills that are lacking. Doing so will help you identify where it makes sense to allocate your finite budget. An example: Baitch is "thoroughly impressed" by his small internal development team and credits them with excellent custom-built applications. But ensuring that each line of the code behind those applications is secure isn't necessarily a strong suit. "They don't have the holistic view of security in mind," Baitch said. So Bob's Stores enlists a third party, Veracode, to test its applications for potential security holes.

4. Outsource Your Weaknesses
If Baitch had to start over, one thing he'd do differently would be to embrace outside help earlier. It can run counter to the do-it-yourself ethos common among many SMBs. It can also require letting go of some ego. But outsourcing your skill shortages can turn them into strengths. "Leveraging third-party tools from the beginning would probably be the number one thing I would have changed, as opposed to having a learn-on-the-job type thing for developers," Baitch said.

5. Know Your Endgame
Baitch is quick to point out that no two companies are quite alike. Therefore, there's no set of security goals that can be applied uniformly to every SMB. Define what you need to secure and why--then pursue those goals with gusto. PCI compliance was the headliner for Bob's Stores. Your SMB's list might look entirely different. Having clear goals helps reinforce step one--that organizational mindset that understands there are a real reasons for doing X, Y, and Z, rather than considering those variable practices a waste of time. "The endgame has to have everyone on the same page," Baitch said. "It's your job to implement. How you implement is completely up to you, as long as you meet that end result."

Security concerns give many companies pause as they consider migrating portions of their IT operations to cloud-based services. But you can stay safe in the cloud. In our Cloud Security report, we explain the risks and guide you in setting appropriate cloud security policies, processes, and controls. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
3/15/2012 | 1:57:17 AM
re: 5 Steps To Stronger SMB Application Security
Number 4 is good one. Sometimes it can be cost-effective and smart to get some help.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0761
Published: 2014-08-27
The DNP3 driver in CG Automation ePAQ-9410 Substation Gateway allows remote attackers to cause a denial of service (infinite loop or process crash) via a crafted TCP packet.

CVE-2014-0762
Published: 2014-08-27
The DNP3 driver in CG Automation ePAQ-9410 Substation Gateway allows physically proximate attackers to cause a denial of service (infinite loop or process crash) via crafted input over a serial line.

CVE-2014-2380
Published: 2014-08-27
Schneider Electric Wonderware Information Server (WIS) Portal 4.0 SP1 through 5.5 uses weak encryption, which allows remote attackers to obtain sensitive information by reading a credential file.

CVE-2014-2381
Published: 2014-08-27
Schneider Electric Wonderware Information Server (WIS) Portal 4.0 SP1 through 5.5 uses weak encryption, which allows local users to obtain sensitive information by reading a credential file.

CVE-2014-3344
Published: 2014-08-27
Multiple cross-site scripting (XSS) vulnerabilities in the web framework in Cisco Transport Gateway for Smart Call Home (aka TG-SCH or Transport Gateway Installation Software) 4.0 allow remote attackers to inject arbitrary web script or HTML via unspecified parameters, aka Bug IDs CSCuq31129, CSCuq3...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.