China
Africa
Explore chapters and articles related to this topic
Planning
Published in Park Foreman, Vulnerability Management, 2019
When deploying active network scanning on a collection of servers, start with a single server that provides some redundancy, then assess the results. A good starting place is a domain controller in an Active Directory® environment. By initially performing the audit against a single domain controller and assessing the results, it is possible to identify any adverse effects. Then, the deployment can continue outward to larger groups of domain controllers. Once enough confidence has been gained in the directory administrators, you will have momentum to deploy to other infrastructure systems.
CONTINGENCY PLANNING
Published in James A. Scholz, Enterprise Architecture and Information Assurance, 2013
information system, and maintaining these controls on an ongoing basis. Within the family of contingency planning, NIST SP 800-53, revision 3, identifies 10 security controls for your information systems that will help guide you through the selection process and determine what security controls are needed for the impact level of your system. Not all controls are applicable to all systems. The FIPS 199 security categorization determines which controls apply to a particular system. For example, information systems that have availability as a security objective categorized as low impact do not require alternate processing or storage sites, and information systems that have an availability security objective categorized as moderate impact require compliance with only the first system backup control enhancements. Using the FIPS 199 security categorization allows for tailoring of the CP security controls in NIST SP 800-53 to those applicable to the appropriate security control baselines. As shown in Chapter 4, the formula below can be used to help document the decision process and impact level of your information system. When documenting the decision you should include a narrative for each impact decision for future reference. These documents should be, at least, classified as company sensitive and not releasable to outside sources. The formula is Security category information system = {(confidentiality, impact), (integrity, impact), (availability, impact), (authentication, impact)} Decision justification: Confidentiality: The impact level of confidentiality is determined to be H, M, L because the system functions as a {domain controller, financial records store, database, web server}, and in support of the system requirements it has been determined to be a {mission-essential function, non-mission-essential function} system by the {stakeholders, CIO management team, etc.}. The information system {does/does not} contain personally identifiable information (PII) or other mission/business-sensitive data. Integrity: The impact level of integrity is determined to be H, M, L because the system functions as a {domain controller, financial records store, database, web server}, and in support of the system requirements it has been determined to be
Narrowing the scope of failure prediction using targeted fault load injection
Published in Enterprise Information Systems, 2018
Paul L. Jordan, Gilbert L. Peterson, Alan C. Lin, Michael J. Mendenhall, Andrew J. Sellers
This research presents an analysis of a practical implementation of the AFP framework with a more targeted fault load including focused software fault injection, third party memory leaks, third party Central Processing Unit (CPU) over-utilization, and heap-space corruption. The implementation is validated on a Microsoft (MS) Windows Server 2008 Domain Controller (DC) and on an Apache web server. The results showed that targeted fault-inducing loads could create realistic failure conditions on Windows Server 2008, whereas software fault injection alone could not. Furthermore, these failures were identifiable by Support Vector Machine (SVM) and boosted decision-tree statistical learning models, with an average area under the Receiver Operating Characteristic (ROC) curve of .