By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Windows networks and applications are often treated as entirely separate entities. Maybe you have different people maintaining them, maybe the security policies are unique or maybe there's just no budget to support one type of security over another.
Whatever creates the disconnect, the result is usually the same: Without a more complete IT view of Windows security needs, the perimeter will be weakened and there's a good chance you'll have to safeguard your data from more and more security threats.
I recently posed this dilemma to our ITKnowledge Exchange members. I asked how effectively they communicate with different IT groups in their organization, what approaches they take to secure Windows and where their IT loyalties lie (network, applications, etc.).
Some respondents shared their annoyance with the lack of communications among network and applications administrators, while others offered best practices for keeping Windows data secure in spite of what happens at security layers they may not be able to control.
Here are their comments for your consideration:
- Network and applications groups disconnect makes for bad practices
- Windows systems just connect to jacks in the wall
- Effective firewall with a Swiss cheese rule set
- Enforcing a formal firewall exception policy
Do you have comments to add to this discussion? E-mail us and we'll add them to the list.
Do you have comments on this tip? Let us know.