An Introduction to Microsoft Forefront (Part 2)
In part two of this series we will cover other parts of the Comprehensive Microsoft Forefront security suite.
In part two of this series we will cover other parts of the Comprehensive Microsoft Forefront security suite.
This article will take us through the comprehensive Microsoft Forefront security suite.
In this article at The Register, a point is raised; is it even worth disclosing vulnerabilities, considering the ramifications?
In the cryptographic community, disclosure is mortar; it is responsible for the stability of research in the field. Good, secure cryptographic design is a product of the cryptanalytical aptitude that was built before it. Simply put, this means that cryptography, in general, has been successful, due to the fact that cryptanalysts are able to publish results. These results may include practical attacks on applied cryptographic systems, which leads me to wonder – could a cryptanalyst face legal woes in the event of disclosing a cryptographic weakness with the context of this issue at hand? Probably; it's contextual.
Over the decades, the reason we've built progressively better cryptography is because of cryptanalytical results published by fellow cryptographers; younger, maturing cryptographers, such as myself, look to these past results as our foundation. Recognizing and disclosing insecurity is essential for the rethinking and designing of security.
There are nooks and crannies to the disclosure debate that have been investigated over the years, but when all is said and done, disclosure, in general, is a necessity. Errors resulting in insecurity are inevitable, but they cannot be shrugged off as a matter of course, then pushed to the side. Correctness and security are both crucial.
As humans, we have an unspoken duty of defending our basic human rights. If there was a bill of security rights, disclosure would be on there, without a doubt; it wou
This article is a quick step-by-step guide for performing a Disk Performance Test with the GUI version of the tool JetStress 2004.
In this article I’ll begin my trek through the installation and configuration of SBS 2003 SP1. The installation is a clean installation. I will not discuss upgrade scenarios in this series. While I realize that this isn’t the most common deployment scenario, it allows me to discuss the salient points of the CEICW and subsequent ISA firewall installation and configuration.
In the final installment of this two-part series, we'll cover two closely related collision attacks – the birthday attack and the meet-in-the-middle attack. We'll conclude by emphasizing the importance of simplicity through conservatism, and establishing a "golden rule" for instantiating the lengths of many cryptographic values.
This article takes a look at a neglected area of most computer security professionals' training: how to deal with the ethical issues that can – and invariably do – crop up during the course of doing your job.
In part five we take the IT professional through strategies of offsite recovery and potential solutions that could be recommended to businesses for recovery. The importance of pre-disaster preparation is highlighted and the fact that just basic preparedness is done in the event of disaster proves to be worth the time and cost invested.
In part four of the Disaster Recovery series the important project definition phase is covered, disaster recovery strategy as well as project mile stones. Importantly materials that should be stored offsite and best practice has also been highlighted.
Site links are a critical part of building Networked Windows Networks – How do Domain Controllers speak to each other without having synchronization problems? Network bandwidth being over utilized can play havoc with your network, at the same time affecting your Windows Server 2003 systems by creating errors in your logs seen in the Directory Services Log in the Event Viewer on our Domain Controller (DC). In this article we discuss things to consider when planning and designing site links.