Cisco ise 2.4 deployment
![cisco ise 2.4 deployment cisco ise 2.4 deployment](https://www.cisco.com/c/dam/en/us/td/i/400001-500000/410001-420000/410001-411000/410617.jpg)
Is there a corporate security policy that governs the use of technology assets and restrictions on them? May I see it if there is? Can we create one if there is now?.
![cisco ise 2.4 deployment cisco ise 2.4 deployment](https://1.bp.blogspot.com/-Z2UyTD4zgLI/WTLkz5D4iII/AAAAAAAAAgE/qHYJp9KEiK8Uyoy9cwbZdvDGEucxH2vKACLcB/s1600/Screen%2BShot%2B2017-06-03%2Bat%2B9.56.45%2BPM.png)
Will we be restricting access dynamically based on changes to those corporate assets?.Will we be tracking and controlling corporate assets?.Is guest access a requirement? If so, is there a requirement to track who is coming onto the network as a guest?.Will we allow BYOD? If so, will we allow those endpoints to talk to internal assets? What level of control over those endpoints do we require?.Are we going to be preventing east-west traffic as well as north-south?.Is complete or partial network segmentation required?.Do we need to restrict access based on roles, endpoint type, etc?.Some of the questions I would pose include: Different companies, industries, regulations, auditors, etc might guide each company to have a different security policy so you should deploy your ISE implementation to compliment that security policy. You should never start planning your ISE deployment without having a company security policy in mind and stating your goals. One important thing to remember with ISE is that it's a control for your company's security policy but it's not supposed to write your security policy for you and it shouldn't dictate what your corporate security policy is. In this post, I'm going to really focus on what I do to make an ISE implementation successful. Like any piece of infrastructure, all the best configurations in the world won't help you if it's not design properly. In this blog post, I'm going to get into designing, scaling and deploying ISE.