==== 3. Security Matters Blog ====
by Mark Joseph Edwards, http://www.windowsitpro.com/securitymatters
Check out these recent entries in the Security Matters blog:
Santy Claws at Vulnerable Web Sites
Dashing through the holes, a new worm designed as play, through the shields it goes, hacking all the way... Read the rest of the jingle in this blog item on our Web site.
http://www.windowsitpro.com/Article/ArticleID/44903/44903.html
Discovering 44 Security Holes Doesn't Make the Grade
What if you were taking a computer science course and a primary requirement is that you must discover 10 new security holes or you won't get a passing grade. Could you do it? Hard to say, right?
http://www.windowsitpro.com/Article/ArticleID/44869/44869.html
==== 4. Instant Poll ====
Results of Previous Poll:
Are Instant Messaging (IM) or peer-to-peer (P2P) threats a problem on your network?
The voting has closed in this Windows IT Pro Security Hot Topic nonscientific Instant Poll. Here are the results from the 30 votes.
17% - Yes, both are
7% - Yes, IM threats are
20% - Yes, P2P threats are
57% - No
(Deviations from 100 percent are due to rounding.)
New Instant Poll:
Do you think Microsoft should improve its security alerting process?
- Yes, it should send alerts about all security updates
- No, the process works fine for me the way it is
Go to the Security Hot Topic and submit your vote
http://www.windowsitpro.com/windowssecurity#poll
==== 5. Security Toolkit ====
FAQ
by John Savill, http://www.windowsitpro.com/windowsnt20002003faq
Q. After I upgraded from Windows 2000 Server to Windows Server 2003, I received an error about the Enterprise Domain Controllers group's access to certain Group Policy Objects (GPOs) in Group Policy Management Console (GPMC). What's causing this error?
Find the answer at
http://www.winnetmag.com/Article/ArticleID/44864/44864.html
Internet Connection Firewall Configuration Problems
(One message in this thread)
A reader writes that he's using Windows Server 2003 with McAfee Antivirus, and the system also runs Microsoft IIS 6.0. He has tried to implement the Internet Connection Firewall to allow only ports 80 and 3389 for remote desktop use. He said the configuration works fine initially but after 5 to 10 minutes (or a few remote login attempts) some sort of problems arises in which the server won't allow remote logins. IIS continues to respond fine. Can anyone help him determine what the problem is? Join the discussion at:
http://www.windowsitpro.com/Forums/messageview.cfm?catid=42&threadid=128762