Cybersecurity

Trojan Horse Primer

A Trojan horse is a program in which malicious or harmful code is contained inside apparently harmless programming or data in such a way that it can gain control and do its chosen form of damage, such as erasing the data on your hard drive. A Trojan can cause massive harm to you and your systems and worse yet, may turn your system into a killing machine as well! Lets look at Back Orifice specifically so we can highlight why a tool like this can get ugly if installed on your systems.

Auditing for Increased Security (Part 1)

You will need to Audit your systems for enhanced and increased security. When Microsoft laid out this objective, they were most likely thinking about building your security strategy up with Defense in Depth. This strategy is outlined as a way to avoid depending on one single protective measure deployed on your network. In other words, to eliminate the feeling of being secured because you implemented a firewall on your Internet connection you should implement other security measures like an IDS (Intrusion Detection) system, Auditing and Biometrics for Access Control.

Configuring Windows Server 2003-based ISA Server Firewall/VPN Server to Accept inbound NAT-T L2TP/IPSec Calls

Road warriors depend on VPN access to the corporate network. Just one file, one presentation, can make the difference between happy holidays for everyone and standing in line at a soup kitchen. Windows Server 2003 supports PPTP, L2TP/IPSec, and the new RFC IPSec NAT Traversal VPN protocol. IPSec NAT-T allows your road warriors to use IPSec to connect from anywhere. Check this article to find out how.

What’s New in Windows Server 2003 IPSec (Part 2)

In Part 1 of this two-part article, we took a look at one of the most important new additions to Windows Server 2003’s implementation of IPSec: the new and improved IP Security Monitor. You learned about its new look (MMC console) and increased functionality. In Part 2, we’ll discuss the other improvements that Microsoft has made to IPSec in Windows Server 2003. Many of these are small things, but taken together, they make IPSec more secure and easier for administrators to manage than ever before.

What’s New in Windows Server 2003 IPSec (Part 1)

With the release of Windows Server 2003, Microsoft has made improvements to a number of their operating system security features, including several new features for IPSec. In this two part article, we’ll focus on what’s new for IPSec in Windows Server 2003, and show you how to use its new features to make it even easier for you to ensure secure communications across your network. Part One covers the IP Security Monitor, which has a brand new look and added functionality.

Windows Server 2003 System Security Analysis ‘Quick and Easy’

In this article we will look at demystifying the simple analysis of a Windows Server 2003's security posture. Too many times, administrators seem confused about how to do an initial security analysis test on a newly minted Windows Server 2003. (Or 2000 for that matter) In this article we will look at how to perform this very quickly, very easily with Windows Server 2003. This article will cover the steps needed to create the Security Database and perform the analysis on your Windows Server 2003 system.

Reducing “Human Factor” Mistakes

Nowadays companies and organizations face the problem where massive attempts at illegal intrusions hit their network on a daily basis. In spite of the latest technological improvements in security, it's still the network users who are often unknowingly inviting security breaches through carelesnes and a lack of awareness. This paper will try to summarize various mistakes done by system administrators, company executives and of course the end users, and will also provide you with useful strategies that will definitely help you reduce or completely eliminate the mistakes.

Scroll to Top