When was the most recent Windows desktop auditing? If you are like most network administrators working with me, then you are lucky enough to use a standard Desktop mirroring. A formal audit of everything on the desktop seems impossible.
Maybe you want to standardize your Windows configuration settings. Or you need to have a better grasp of terminal security. You may even want to clean up your organization's software licenses. Regardless of your goals, there are a few things you need to remember that can maximize your desktop auditing results.
Defining the Needs of Windows Auditing
First, why do you want to audit Windows configuration? 50% of any successful projects —— audit or not audit —— depends on reasonable settings expected. In addition to ensuring that the right IT staff is involved, you should determine which non-IT person needs to check the desktop environment.
Consider human resources, legal, regulatory compliance, and internal auditors. To take into account more stringent requirements than current businesses, representatives from these areas have a say in login advertising, local security policies, software licensing, audit logging, and more. Even sales people and customer service have a say in desktop configuration.
You need to ask all affected people. Some people may think that you are crazy, they think that "desktop audit is an IT thing". So let them know how software auditing affects the entire organization and how the assistance they make in the decision making process affects long-term business.
Know your business system
Understand what it is. You can't audit things you don't understand. It's easy to overlook certain desktop systems, such as desktop systems that belong to salespeople, remote offices, or warehouses. However, if you want to get accurate information on the current Windows desktop usage, you will eventually need to cover all aspects.
Start with your network topology diagram. Check which hosts are dynamic from a network port scanner such as nmap or SoftPerfect network scanner. Just don't forget the networks that are not directly accessible via the LAN. A poor desktop audit is often forgotten by systems that are not particularly obvious, but these systems should normally be under the control of IT.
Use security vulnerability assessment. If you are performing a regular vulnerability scan or have more formal internal security assessments, you will get a lot of information that you can dispose of. You can use the information in the Vulnerability Scanner report to analyze existing desktop scenarios and trends over time, such as which changes, which have not changed, and other significant improvements (such as third-party patch management and localization) security strategy). If the running scan has a visa, then tools like Nexpose and LanGuard can provide amazing insight and verification information about the runtime of the Windows system.
Remember, desktop auditing is not secure
Of course, security is actually a top priority for almost all Windows desktops, and an ongoing security assessment does complement your desktop auditing. But there are many more, including collecting software information to ensure compliance, compliance with the upgrade plan, and monitoring application usage to ensure consistency and support.
In addition, regular enterprise system inventory (such as BYOD strategy) is also a good idea. The more information you know about the environment, the better decisions you can make and the better your execution.
Windows configuration is a dynamic job
Most people can't keep up with the speed of technology changes. Don't think of Windows desktop auditing as a one-time job. Imagine the various decisions in your personal life or everything in your business that relies on a one-time snapshot of information all year round. Desktop auditing should be part of your ongoing IT program and may be done annually, perhaps in conjunction with periodic vulnerability assessments.
Before you start a desktop audit, the more time you spend ensuring the proper configuration of your Windows, you will have a greater chance of improving your productivity and reducing unnecessary hassles. It's best to start with a small software audit, especially if you have never done an audit before. Build your audit engineering and toolset, and Windows Desktop Auditing will be another well-functioning IT feature.
Successful Windows auditing helps IT administrators optimize workstation configurations, improve security and simplify system management.
I. Introduction to DHCP: The full name of DHCP is the Dynamic Host Configuration Protocol (Dynamic H
The role of the DHCP server: DHCP server Needless to say, without running a DHCP server, IP
Experimental Line Connection Diagram: DCRS-5526S Configuration: Assume that the name of the DHCP ad
Experimental software environment: virtual machine Vmware Workstation10.0, CentOS 6.5 32 bit 1, auto
Ordinary files can also be a means of black/gut intrusion
The server must know a few knowledge
Windows server2003 speed up method
Prompt for password when resolving Web access
Must understand the server five problems
Key Points Affecting SQL Server Performance
Server setup diagram Description
Four Considerations for Performing Windows Desktop Auditing
The application and principle of DHCP in the enterprise network campus
What programs are loaded in Vista security mode
How to build win10 delete folder Win10 create anti-duplication folder tutorial
How to display control panel icons on Windows 8 desktop
Win7 application does not work properly How to solve
Playing the game network with win 7 system has a high latency?
How to modify the installation location of Win10 application
Win10 preview version 10159 can not be upgraded? Try these 5 solutions
WINDOWS 2003 IIS failed to start