Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
NoVirusThanks OSArmor
Message
<blockquote data-quote="ForgottenSeer 58943" data-source="post: 713284"><p>Not to derail the thread, so just to answer this. I will share it. I'm switching to zone based security away from so many policies. When zoning, the perspective of the actual components, users, and threats dictates a given device’s zoning requirements and what zone those devices are placed in. Theoretically perspective actually defines the security posture.</p><p></p><p>Network zoning is a traditional method, used for decades which went by the wayside in favor of policy based and VLAN networking. I'm bringing Zoning back because it has many advantages and has decades of proven track record. VLAN tagging means that data is still over the same wire (and yes, they can be intruded upon under some conditions), just that the tag is ignored or recognized if it is needed. Zoning means it's isolated at the physical hardware level and bundled up behind security necessary for each zone. This is a 'trust barrier' ensuring I can move devices in and out of various zones as needed depending on their threat surface. An attacker coming in on an untrusted (DMZ) zone would have no facilities to attack. An attacker coming in on a semi-untrusted zone such as WAN1 might have slightly more attack vectors, but largely be limited to non-user space firewall/UTM, and specific ports/protocols permitted in that zone. Someone in the green zone may have unfettered access to the network, but that will likely be a hardened system running something like Secured Debian.</p><p></p><p>You get the idea.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 58943, post: 713284"] Not to derail the thread, so just to answer this. I will share it. I'm switching to zone based security away from so many policies. When zoning, the perspective of the actual components, users, and threats dictates a given device’s zoning requirements and what zone those devices are placed in. Theoretically perspective actually defines the security posture. Network zoning is a traditional method, used for decades which went by the wayside in favor of policy based and VLAN networking. I'm bringing Zoning back because it has many advantages and has decades of proven track record. VLAN tagging means that data is still over the same wire (and yes, they can be intruded upon under some conditions), just that the tag is ignored or recognized if it is needed. Zoning means it's isolated at the physical hardware level and bundled up behind security necessary for each zone. This is a 'trust barrier' ensuring I can move devices in and out of various zones as needed depending on their threat surface. An attacker coming in on an untrusted (DMZ) zone would have no facilities to attack. An attacker coming in on a semi-untrusted zone such as WAN1 might have slightly more attack vectors, but largely be limited to non-user space firewall/UTM, and specific ports/protocols permitted in that zone. Someone in the green zone may have unfettered access to the network, but that will likely be a hardened system running something like Secured Debian. You get the idea. [/QUOTE]
Insert quotes…
Verification
Post reply
Top