Network Security Library
Javascript Feeds    RSS Feed    Security Dashboard    SearchSecurity.com
About | Contact | Advertise | Site Map

Auditing


{LANG_NAVORIGIN} Vulnerability Management Auditing

Subcategories


Pen Test



Low-Level Enumeration With TCP/IP
We've all used most of the popular stealth scanning techniques out there right now. Tools such as nmap are excellent for enumerating remote hosts with increasingly complex techniques. The only problem being most of the nmap users out there do not take the time to find out exactly what is going on behind the scenes to make these scans work. In the following paragraphs I will attempt to explain the theory and concept behind many of today's advanced scanning techniques, and try to show you what is going on behind the scenes with them.
By Randy Williams, 02/16/2005


Case Study: Automating Common InfoSec Auditing Tasks on a Windows 2000 Network
Policies are only as good as the procedures used to implement them. When the procedures are too cumbersome or time-consuming, it is likely that policy compliance will suffer. Unrealistic procedures can lead to “implemented policies” that are weaker than the stated policies. Conversely, ensuring that procedures are easy to implement has the effect of making full policy compliance more likely. In this case study, we will examine how automating information security audit procedures at a university had the effect of increasing security through increased policy compliance. We will discuss three stated policies, their associated procedures, and how poorly designed procedures led to weak “implemented policies.” We will then discuss how the procedures were automated, and, finally, discuss the effects of the automation on the university’s overall security stance.
03/28/2004


Security Auditing A Continuous Process
Does your company have internal auditing? Do they think audits are necessary? Are they willing to follow through on an audit, from start to finish? Many think audits are unnecessary and useless. When an audit is completed, the outcome isn't taken seriously. Maybe they are even compromised and manipulated internally. What do you think? Could it take too much time, money, or be an inconvenience. Whatever the reason, there is no excuse for not conducting internal audits. Having timely and thorough audits is a critical piece of an organization but in many cases, they are not being performed, at least in a timely manner. Internal audits are a never-ending process. I would like to help you determine how to successfully configure your W2K file and print server, monitor your server, have an action plan and be prepared for a successful security audit on that server. Although this audit will center on W2K servers, the same principals can be applied to other server audits.
By Pam Page, 03/24/2004


The Institutional Need for Comprehensive Auditing Strategies
This paper begins with a definition of auditing, as the word "audit" can mean different things to different people, and contrasts the use of auditing in data processing's early days to its function in the world of IT, today. The intent is to show that the interconnectedness brought about by business conducted over the Internet alters the scope and approach of audits. Audits once performed at the application or line of business level, though still necessary, are no longer sufficient to surface and assess all exposures created by the new environment. Further arguments elaborate on the impact and implications of the technology that have enabled e-Business and show not only the distinctions between past and present environments, but also become a requirements list for a comprehensive audit strategy. Finally, a series of recommendations are made that outline the foundational elements an organization needs to enable an effective strategy.
03/24/2004


Conducting a Security Audit: An Introductory Overview
The word "audit" can send shivers down the spine of the most battle-hardened executive. It means that an outside organization is going to conduct a formal written examination of one or more crucial components of the organization. Financial audits are the most common examinations a business manager encounters. This is a familiar area for most executives: they know that financial auditors are going to examine the financial records and how those records are used. They may even be familiar with physical security audits. However, they are unlikely to be acquainted with information security audits; that is, an audit of how the confidentiality, availability and integrity of an organization's information is assured. They should be. An information security audit is one of the best ways to determine the security of an organization's information without incurring the cost and other associated damages of a security incident.
03/22/2004


Computer Audit FAQ
Answers Frequently Asked Questions about computer audit (aka systems audit, IT audit etc.). Offers pragmatic guidance to those new to computer audit, including those about to be computer-audited for the first time. Presented as a web page and now with a downloadable PDF file for off-line reference and printing. Enjoy!
By Gary, 03/05/2004


Network Security Audit (Part II)
In the First part of Network Security we had a brief overview of the areas that are to be considered on accessing a network's security and also we looked into a few points in each of Management and Administration areas.
03/02/2004


An Audit of Active Directory Security, Part 5
This is the fifth and final installment in a five-part series on auditing Active Directory security. The first article in the series offered a brief introductory overview of Active Directory. In the second installment we examined some of the security implications of the AD?s default settings. The third article looked at LDAP, SASL and Kerberos in the context of AD security. The fourth part looked at some potential security concerns related to the Configuration Naming Context in AD. This article will examine some issues surrounding the multi-master replication scheme.
02/17/2004


An Audit of Active Directory Security, Part 4
I'd like to note that this particular article has been the longest in development in the series so far; the reason being that playing with the Configuration Naming Context (CNC) tends to crash the directory service, sometimes in very hard-to-recover ways, such as rebuilding the server.
02/17/2004


An Audit of Active Directory Security, Part 3
This article is the third in a series devoted to discussing security issues surrounding Active Directory, also known as AD. The first article offered a brief overview of Active Directory. The second The second article offered an overview of the security implications of AD's default settings. This article will offer an overview of the relationship between LDAP, SASL and Kerberos, and examine what they have to do with Active Directory Security.
02/17/2004


Page: 1 2


Application Security
Architecture
Authentication
Certifications
Disaster Recovery
Encryption
Enterprise Security
Exploits
Firewall
Incident Handling
Intrusion Detection
Laws and Regulations
Malicious Code
Operating System
Security Basics
Security Management
Security Policies
Security Tools
Standards
Vulnerability Management
Web Security
Wireless Security

Newest
Highest Rated
Most Viewed
Reference

Javascript Feeds
RSS (New Papers)
Security Dashboard

About SecurityDocs
Advertise
Contact

Valid HTML 4.01!
Valid CSS!


Unless otherwise noted, all paper copyrights are owned by the author. The rest copyright 2003-2005 TechTarget

Privacy : Contact