There is a lot of buzz out there right now about Telework Solutions for Government as many agencies are making the transition that so many Corporations have already completed. Personally, I haven’t worked full time in an office since pre-1996 and can’t imagine wasting that much time every day on preparations and commuting for no real purpose other than donuts, coffee and the latest office gossip.
Work is an activity, not a location in today’s professional world with pervasive networking capabilities and the Government is getting on board under the leadership of the current administration.
If you want to get a feel for the progress and momentum around this, check out the public/private partnership at the Telework Exchange site focused on eliminating the Telework Gridlock. Cisco is one of the sponsors of this activity because we see the value, have lived it for better than 15 years, and can offer solutions to help make this a reality for our Government customers. Read More »
Each year a considerable part (up to 30% in some cases) of IT budgets is funneled towards device troubleshooting. It is no surprise therefore that after security, maintaining lean operational efficiency is the next most frequent concern regarding enabling a BYOD (Bring Your Own Device) model.
Suppose you have allowed personal devices to connect on your corporate network, and you get a helpdesk call from a disgruntled employee that can’t access certain resources. How would you go about addressing the issue? In this video, Saurabh Bhasin, Product Manager of the Cisco Prime Network Control System (NCS) – a newly launched platform for unified wired and wireless network management – answers the troubleshooting question.
Allowing personal devices on the corporate network can make any IT professional cringe. Security is naturally a top concern – and the topic of today’s blog.
One dimension of security is about enabling network access. To do that properly, you would need to design and enforce a mobile device access policy, which may include attributes such as: what the device is, who the user is, where and when access is requested, and the health (posture) of the device. Another dimension of security is about maintaining overall device integrity regardless of the network (corporate or otherwise) it connects to.
In this video we only address the first. Cisco’s solution is based on a newly launched product, the Cisco Identity Services Engine (ISE). Watch the video to learn:
What is the Cisco ISE?
Can I treat corporate devices differently from personal ones?
What about guests in the organization, do I need a separate system?
Hope you found last week’s inaugural blog on the “Tablet Welcomed.” series interesting enough to come back.
Today, I am sitting down for an interview with Brett Belding, who was instrumental in designing a mobile device access policy for Cisco, in his role as the Senior Manager of IT.
I met Brett over Cisco Telepresence one early morning (when I typically I am still asleep, let alone in the office) to accommodate his Eastern time zone schedule. For the videophile readers, I should say that I pointed my camera directly to the Telepresence screen, which is why you may notice my reflection at certain points. However, this amateur video alone could be a case study for the quality of Cisco Telepresence.
Authored by : Kent Wong, Product Manager, Technical Services
It was a evening like any other. The Lone Admin walks into a his local watering hole to relax after a full day of battling issues and keeping his company’s network safe and secure. He is known somewhat as a miracle worker, a conundrum wrapped in an enigma. Even against the most sinister of network issues he is able to stand his ground and find resolution all by himself. How does he do it? None of his peers know.