Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

3/6/2012
12:25 PM
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
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...