How To Administer Risk Associated With Web Applications
Corporate around the world are working on innovative ideas and building web based applications as they provide flexibility, low maintainability cost, rich functionality and adds up the benefits of its own. Companies offering services are also major player and they will stay in the market for very long time (as per survey). Software as a service (SaaS), in particular, is playing out pretty well in today’s economy, according to IDC, which predicts the sector will see a 36 to 40 per cent growth in 2009. Yet many organizations, especially at the enterprise level, worry about offloading corporate data to a third-party vendor. Will security risks increase? What happens when reliability begins to suffer? How can they access critical data/systems during an outage? These are valid questions, but many experts actually think that your data is safest with a credible third-party whose business in effect is (or should be) managing the security and reliability of data across many customers. After all, if a vendor screws up, it will lose revenue, customers and market share in a heartbeat. Still, due diligence is imperative for any SaaS implementation. Here are 10 risk administering factors to consider when offering web-based software to your employees. 1: Identify a low-penalty area of the business to serve as your first SaaS project The first time you enter an arrangement with a vendor to host software and data for you, avoid outsourcing a highly visible area of your business. If HR is not strategic to profits that might be one place to start. Save the high-stakes CRM project for later, when you have learned a few best practices. 2: Assess your risk Before you can come up with metrics and other requirements for vendors, you need to determine exactly which business and IT priorities of the data/system you want to outsource and what will be the fallout of any sort of breach or data loss. How do your internal requirements for encryption, network security, privacy, disaster recovery, auditing and monitoring align with the services provided by the vendors under consideration? 3: Choose vendors carefully I would recommend you to select vendors with a long track record of providing web-based software and services. You may have to pay more for established vendors, but doing so will likely lower your risk. Let someone else do the thinking (and risk) ahead of you. 4: Do a deep dive on your SaaS vendor’s security infrastructure and approach It’s not out of the question to request a third-party audit of the company’s security systems and policies. What security certifications does it hold? Is the company compliant with any relevant industry regulations, such as PCI DSS for credit card transactions? Following is a checklist you can use:
- How and where data encryption is used (for instance, on backups as well?)
- The quality of the network defenses in the data center
- How authentication and secure connections are handled
- The use of data loss protection (DLP) technology
- The question of multi-tenancy, since you’ll be sharing computing resources with other customers