"A Solution for Private Cloud Security" series of three papers on private cloud security. With increasing numbers of organizations looking to create cloud-based environments or to implement cloud technologies within their existing data centers, business and technology decision-makers are looking closely at the possibilities and practicalities that these changes involve.
There are three documents in the downloadable .zip file:
- A Solution for Private Cloud Security – Service Blueprint
- A Solution for Private Cloud Security – Service Design
- A Solution for Private Cloud Security – Service Operations
This document set represents the v.95 beta of this document set.
Please write to Tom Shinder at firstname.lastname@example.org if you have recommendations or would like to review these documents for the official v1 release.
Note: Tom is doing great job in building Reference and Security Architecture for Private Cloud
Hyper-V team just published a new KB article called “Configuring Certificates for Virtual Machine Connection” that talks about the way Hyper-V uses certificates and how to set it up. They also explain why we need them, something that might help new users and customers. This article provides information to folks who need to set this up and to folks who wanted to know how to work around wildcard certs.
It was put together by a member of our Test team, Krishna, at the request of our product support folks and now it’s here for you.
Enjoy it 😀
This security update resolves a privately reported vulnerability in Windows Server 2008 Hyper-V and Windows Server 2008 R2 Hyper-V. The vulnerability could allow denial of service if a malformed sequence of machine instructions is run by an authenticated user in one of the guest virtual machines hosted by the Hyper-V server. An attacker must have valid logon credentials and be able to log on locally into a guest virtual machine to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
Some times you may have to change your Kaspersky Administration Kit IP address for restructuring purpose in your network.
You may face problem that all your agents appears offline in the Administration Kit console..all the clients appears with thier old IP.
The reason that the Kaspersky network agent is not able to contact the Administration Kit so it will not able to update its inforamations or get updates or policies from Administration Kit.
T keep the workstations connected to the Administration Kit you may to install another copy of Network Agent to each computer so that the admin kit can communicate again with the workstations.
In my case that solution does not help me a lot..I still facing the same problem so I used that batch to the agents and it works.
cd Program Files\Kaspersky Lab\NetworkAgent
klmover -address (New IP of AIK)
Promises patch to plug hole that’s been exploited for weeks
Microsoft Corp. yesterday warned of a critical vulnerability that affects users of Word running on Windows 2000, XP and Server 2003 SP1 — several weeks after one security company first reported an exploit and a day after a second vendor confirmed ongoing attacks.
In an advisory posted Friday, Microsoft acknowledged “public reports of very limited, targeted attacks” that exploit a bug in the Microsoft Jet Database Engine, a Windows component that provides data access to applications including Microsoft Access and Visual Basic.
According to Symantec Corp., however, the attacks Microsoft described used malicious Word 2000, 2002, 2003 and 2007 documents, which in turn call up the vulnerable Jet .dll (Dynamic Link Library file).
“We believe that the issue being described [by Microsoft] is one described on March 20, 2008, by Elia Florio of Symantec Security Response,” the security firm told customers of its DeepSight threat-analysis network on Saturday. “He notes a recent discovery, by Panda Security, of a possible zero-day exploit observed in the wild.”
Panda researcher Ismael Briones had blogged about the vulnerability nearly three weeks ago, but said Microsoft had dismissed his report of an in-the-wild exploit. “Microsoft replied that they would not fix these mdb vulnerabilities, as it seems they will not acknowledge vulnerabilities which are from .mdb files,” Briones said in his March 3 post.
“You appear to be reporting an issue with a file type Microsoft considers to be unsafe. Many programs, such as Internet Explorer and Outlook, automatically block these files,” Briones reported Microsoft as telling him in its e-mailed response.
Last week, however, Symantec researchers analyzed an exploit that circumvented the .mdb file format blocking in Outlook by simply renaming the file to a format the e-mail client accepted. “In fact, it is possible to call msjet40.dll directly from Word, without using Access at all,” claimed Symantec’s Florio in a Thursday post. “In this attack, the .doc file uses mail-merge functionalities to import an external data source file, and so it effectively forces Jet to load the malicious Access sample.”
Florio also noted that there are at least two unpatched bugs in Jet that have been exploited by hackers. One of those bugs was reported three years ago.
Microsoft said that users running Word on machines powered by Windows Vista and Windows Server 2003 SP2 are not at risk because those operating systems include a different version of Jet.
Although Microsoft downplayed the threat, spokesman Bill Sisk confirmed that a patch was on the way. “We currently have teams working to develop an update of appropriate quality for release in our regularly scheduled bulletin process or as an out-of-band update, depending on customer impact,” he said in a post to the Microsoft Security Response Center’s blog.
Until a fix is available, Microsoft said users and IT administrators could disable Jet or block .mdb files at the gateway.
The next scheduled Microsoft patch day is Tuesday, April 8.
Source : Computerworld By Gregg Keizer
The ISA Server Best Practices Analyzer (BPA) is a diagnostic tool that automatically performs specific tests on configuration data collected on the local ISA Server computer from the ISA Server hierarchy of administration COM objects, Windows Management Instrumentation (WMI) classes, the system registry, files on disk, and the Domain Name System (DNS) settings.
The resulting report details critical configuration issues, potential problems, and information about the local computer. By following the recommendations of the tool, administrators can achieve greater performance, scalability, reliability, and uptime.
The ISA Server Best Practices Analyzer is supplied with two supplemental tools.
• The ISA Data Packager enables you to create a single .cab file containing ISA Server diagnostic information that can be easily sent to Microsoft Product Support Services for analysis.
• BPA2Visio generates a Microsoft Office Visio® 2003 or Visio 2007 diagram of your network topology as seen from an ISA Server computer or any Windows computer based on output from the ISA Server Best Practices Analyzer Tool.