I know I read it somewhere but cannot find it now, does anyone know of a Cisco document that talks about exactly how the Windows OS for CallManager is hardened? There are many docs that say it is but I need to know HOW exactly.
I don't know about the Cisco flavored Windows OS being "hardened" but I do know it doesn't contain unnecessary components. The more components removed from the OS allows for fewer things to be exploited. This is why you MUST get the patches for the OS from Cisco always and NEVER Microsoft.
We implement numerous "tech controls" for security purposes that harden the servers. Our security nazis wanted us to use the same controls for the Call Manager. We complied until we ran into problems with them. I guess what I'm saying is, based on my memory of the tech controls we tried, I don't think the Cisco OS is "hardened". I remmember one tech control was changing something like minimum password length...real basic things that a "hardened" OS would have as a standard.
Be sure to use the Cisco Security Agent always! No need to rate this post. I don't have a link to the requested documentation. I just thought I'd share a little of what I have experienced. : )
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...