Tuesday, September 12, 2006
Becoming Chief Security Architect
1. They must have a vision and no it should be I see stupid people...
2. They should be marketers but not just to internal folks. They should also market issues that are important to enterprises such as XACML, software vendors writing secure code and industry analysts covering open source projects next to proprietary closed source offerings.
3. Be courageous. Most folks will follow you even if your decision is not the most popular choice.
4. Stick your neck out. Being a problem solver requires sticking one's neck out. Facilitating solutions that meet the enterprise objectives may require challenging the status quo...
Links to this post: