"They’re not jumping on this because, first, not all the SaaS has all the required security environment already and, second, the agencies themselves are going through trying to find their own security set of requirements." says Kazem Safari.
The government sector is a voracious user of IT services. In this podcast we examine what issues are keeping federal government agencies from jumping on the bandwagon for Service Management, SaaS and the Public Cloud. Kazem Safari brings his many years of experience in this field to give us some insights and help us understand some of the requirement tradeoffs that need to be considered. Some of the factors discussed are at risk tolerance and vendor evaluation,
Kazem Safari, senior manager for R&D Program Management at BMC Software, has more than 25 years of experience in senior level management of successful enterprises in global executive management, IT, engineering, SaaS product development/deployment, operations, professional services, program management, business development, and sales operations. He is responsible for managing the Remedy On Demand for Public Sector program. Prior to joining BMC, he served as managing director and one of the founders of Symfonia, as program general manager at GTSI, as executive director of Global One, and as head of Multimedia Systems. Safari is PMI PMP and ITIL Foundation 3 certified. He holds a BA in Computer Science from Southern Illinois University, Carbondale, Illinois.
Security requirements are going to vary from program to program. How does the cloud provider support these various requirements?
The private sector is already taking advantage of SaaS and IT service solutions. Why aren’t federal agencies jumping on this as readily?
If there isn’t any such thing as a risk-free cloud, how does an agency decide what, if any, risk it can tolerate?
What are some of the keys to evaluate services providers in terms of compliance with those requirements?
What makes ITSN running on a SaaS model a secure, reliable and cost effective solution?