Lock down your UC system to prevent the theft or loss of sensitive business information
Companies large and small have embraced VoIP (voice over IP) and unified communications (UC), and malicious parties are there, too. In fact, some research firms estimate that targeted attacks on VoIP infrastructure account for as much as one third of all attacks around the world, in part because companies haven’t secured their VoIP and UC systems as well as other online applications like email. Unauthorized persons can use holes in UC systems to sneak onto your network, access stored business data like sensitive customer information, or commit toll fraud.
Just ask Mitch Davis, the CIO of Bowdoin College, a private liberal arts college in Maine. Before BYOD ever became a global IT trend, according to Mitch, the vast majority of college students were already bringing their personal devices into the campus environment.
These co-eds expected Bowdoin to fully embrace personal mobility, and, upon graduation, these same post-grads expect that their employers will do the same (this year’s Connected World Technology Report findings back this up, with more than 40 percent of recent college graduates/Gen Y employees choosing BYOD flexibility over higher pay).
Bottom line, the rules of the game are changing, and companies must move beyond basic BYOD connectivity to meet employee demands today and tomorrow. To help companies meet these demands, we’ve introduced a comprehensive approach that unifies policy, supports a better user experience and simplifies management to deliver an uncompromised user experience in any workspace. After all, Cisco wants to empower IT managers to allow employees to have their devices and use them too. That means delivering:
A unified security policy across the whole organization – wired, wireless, VPN and now MDM – helping companies set and enforce policies;
An uncompromised user experience over the entire wired/wireless network, across any type of device; and,
Simplified operations and network management to understand application performance from a user’s perspective, accelerating troubleshooting and lowering operating costs.
Like Ray-Ban aviators, BYOD is here to stay. And done the right way, BYOD demands a comprehensive approach to allow current and future employees to work how they want, when and where they want, and on the devices they want – while still allowing IT the control and visibility to sleep at night.
Learn more about our announcement and new technologies here.
By the way, whether you’re a college student or have been working for 30 years, you’re eligible to take the BYOD Challenge and win a trip to 2012 London Olympics – good luck!
Back in January, U.S. Department of Education Secretary Arne Duncan and Federal Communications Commission Chairman Julius Genachowski challenged schools and companies to get digital textbooks in students’ hands by the year 2017. Prompted by countries like South Korea and Uruguay -- which have made similar moves – the Obama administration is seeking to create momentum on this key topic.
Adam Frankel Opens the League Meeting at Houston ISD
Yet when we look around us, most educators and superintendents in the U.S. are left scratching our collective heads as we witness our glacial progress toward fully deployed digital nationwide learning. Lack of data on “what works”, lack of best practices in district-level leadership, and a splintered procurement process are often cited as three major roadblocks to progress. As mentioned in earlier blogs here, Digital Promise’s newly formed “League of Innovative Schools” is hoping to change all that.
Some people say that in the next few years that Infrastructure as a Service cloud deployments will be focused mostly on private clouds. And then they say that enterprises will migrate to public clouds after they have become “experienced” in running a cloud. About a year ago I could really see this story played out. Now, fifteen months after we introduced Cisco Intelligent Automation for Cloud, I have some different points of view. I would have thought that by now that private cloud architectures would have begun to converge to a few standard patterns. This has not happened. The world is still diverging when it comes to both Private and Public cloud architectures.
I do see patterns arising in successful cloud deployments and here are some of the key ones:
#5: Pragmatic Approach: IT shops that come with a long list of RFP requirements and questions take a long time to source a technology provider and to achieve production success. Others that are pragmatic (can I say Agile in their approach) get to cloud quicker and learn from their successes and missteps alike.
#4: They Have a Cloud Instance Roadmap: After a cloud deployment, some IT organizations think that is it, they are done, next project, my move to cloud is complete. Hold it right there, did you know that cloud is not a single step where you through a switch, but a succession of deployments of great scope from one step to the next? A roadmap is needed that covers: hardware, network, storage infrastructure, virtualization technology and release version, management and orchestration software instance version and finally the services that you are offering to the end users and how the service catalog is changing over time. Those that have a roadmap roughed out are generally more successful than those that have a big bang perspective.
#3: Appreciation for Challenge of Management of Change:Moving to cloud is a big change in an operating model; careers are created and new roles are defined. How does an organization move to the new model with different technology, processes and people? When a team proactively manages the change in the non-technical they ensure long term success. It is not just about self service, cloud catalogs, orchestration, domain management and virtualization. It is more about service designers and automation authors and changes in operational processes.
#2: Rise of the Cloud Architect: Since cloud is about a new operating model a new position and role is needed. If you have a cloud project and do not have a cloud architect tying it all together from cost models, to hypervisors, to orchestration and orderable service definitions, you need a organization role tune up ASAP.
#1: A Service Centric Approach: Most people get this one right away. Service centric projects are the key focus for ITaaS. However, I can’t tell you how many times when I am talking to an IT team, the opening bell results in a speeds and feeds conversation around provisioning that piece of infrastructure and that virtualization API. If you ask the question about what services they want to offer their end users for self service ordering you will get a request for more time to answer that question. Service Centric IT shops will take the time to start first with the business requirements and the perspective from the end user point of view. Transform your cloud project approach to a service centric agile project and you will go far.