Operationalize the State Strategic Plan for IT Software Currency May 11,2016

Today’s Speakers Bruce Speyer Speaker Deborah Hujar Moderator Endi Silva Administrator Technology Specialist Director Technology Planning & Policy Policy Analyst, SSP lead

Using the Webinar Tool GoToWebinar Control Panel Grab Tab Hide/show control panel Mic (if allowed) Change to full screen mode Raise/lower hand Technical Assistance Click Help at the top of the Control Panel to access online help and links for Tech Support. Control panel options may vary slightly depending on webinar configuration. Handout Pane Download documents (if any). Question Pane Key questions here. Audio Pane Use Sound Check to configure and test audio and other preferences.

State Strategic Plan for Information Resources 1. Reliable and Secure Services Security, Continuity of Operations, Connectivity 2. Mature State IT Resources Management IT Funding, IT Planning & Governance, IT Workforce 3. Cost Effective and Collaborative Solutions Legacy Modernization, Cloud Services, Shared Services 4. Data Utility Data Management & Governance, Open Data, Data Analytics 5. Mobile and Digital Services for Citizens Mobile Applications, Digital Services, Internet of Things

Actionable Goal: Develop and adhere to a software currency policy that reduces the use of unsupported software and decreases security vulnerabilities in state agency IT systems.

Security #1 Top Security Risks are Unsupported and Unpatched Systems (“Zero-Day” threats are rare & one-time) #2 Security Risk is Insufficient Identity Management 2016 is on-track to more than double the number of incidents of previous years

POLL What percentage of your systems or applications are out of support or considered legacy?

Software Currency Maintain an up-to-date software portfolio to reduce the cost and risk inherent in managing unsupported software products End of Support – no more automatic fixes, no new features or updates Extended Support – security & critical bug fixes only, may be fees Out of Support – adhoc for-fee critical security support Unsupported – completely without support Vendors publish support schedules usually years in advance – be aware

Challenges Legacy Study -- current annual ongoing cost of the state’s legacy portfolio, based on support effort and software license fees, is over $300 million Technical debt accumulates and becomes harder to reconcile.

Software Dependencies

Benefits of Portfolio Planning Portfolio Planning and Deployment are ongoing Roadmap and Technology Standards reduce complexity, increase agility and optimizes resources (costs, consolidation, reliability, maintenance, etc.)

DCS Software Currency When the DCS Program declares N/N-1 levels, the Program recommends that DCS Customers migrate to the new N/N-1 levels within 12 months. Typically N is at least one minor release behind the latest major GA (general availability) version (e.g..1, SP1, RC1, etc.) DCS strives to provide at least a year buffer before any N-1 version is in risk of becoming unsupported. Hardware on a 5 year refresh cycle

Example Software Currency Policy Why is DIR publishing this template? How do I use this template? Why do I need a Software Currency Policy?

Steps to Software Currency 1.Adopt a policy with refresh cycles 2.Develop IT Roadmap and Technology standards 3.Do a portfolio analysis 4.Know what you have and use tools to manage (e.g., asset tracking, PM, etc.) 5.Know the dependencies including budgeting and licensing 6.Have a 1 to 5 year plan

Contact Information Brad Helbig Bruce Speyer Deborah Hujar

Questions