Governance, Compliance, and Risk
BlogInterviewing GuideGovernance Guide
  • Home
  • Governance
    • Policies, Procedures, and Guidelines
      • Policies
        • Policy Life Cycle Steps
        • Creating a Good Policy
        • Types of Policies
      • Procedure
      • Guideline
    • Business
      • Review of Security Requirements for Contracts
        • Request for Proposal (RFP)
        • Request for Quote (RFQ)
        • Request for Information (RFI)
      • Common Business Documents to Support Security
  • Compliance
    • Frameworks
      • ISO 27001
        • Changes from 2013 to 2022
      • SOC 2
        • The Planning Phase
        • Famework Subject Matter
        • Security Management Procedures
        • Prepare for Implementation
        • Initiating a SOC2 Audit
        • Conducting a SOC 2 Audit
      • FedRAMP
      • HITRUST
    • Security Controls
      • Asset Management (AST)
      • Business Continuity and Disaster Recovery (BCD)
      • Change Management (CHG)
      • Compliance (CPL)
    • Auditing
      • Gap Assessment/Analysis
      • Techniques
        • Auditing Cybersecurity Programs
        • Auditing Web Servers and Web Applications
        • Auditing Databases
        • Auditing Storage
        • Auditing End-User Computing Devices
        • Auditing Applications
        • Auditing Cloud Computing
  • Risk
    • Frameworks
  • Customer Security
    • What is Customer Security
    • Security Questionnaires: Questions
      • Security Governance
        • Does your organization conduct an annual independent information security review and act upon the fi
        • Does your organization have a documented Cybersecurity Policy or Information Security Policy?
        • Does your organization have a formal policy on the use of mobile devices?
        • Does your organization have a formal policy for remote working that includes security?
        • Does your organization have a documented Acceptable Use Policy
        • Does your organization have a documented Data Classification Policy?
        • Does your organization have a documented Access Control Policy?
        • Does your organization have a Password Policy?
        • Does your organization have a documented Backup Policy?
        • Does your organization enforce a Clear Desk and Screen Policy?
        • Are your organization's information security policies available to all employees?
      • Risk Assessment and Treatment
        • IT & Infrastructure Risk Governance
        • IT & Infrastructure Risk Assessment Life Cycle
        • Third-Party Risk Management
      • Asset and Information Management
        • Asset Management
        • Information Management
        • Media Security
        • Physical Media Transmission
        • Data Transmission
        • Encryption
        • Page 1
      • HR and Personnel Security
      • Operation Management
        • IT Operational Procedures
        • Change Control
        • System Acceptance Criteria
        • Time Synchronization
      • Access Control
        • Access Provisioning
        • Access Revocation
        • Authentication
        • Access Reviews
        • Password Controls
        • Remote Access
      • Application Security
        • Application Security Roles and Responsibilities
        • Secure Architectural Design Standards
        • SDLC
        • Web Server Security
        • API
        • Mobile Application Security
      • Incident Event and Communications Management
        • Cybersecurity Incident Management
        • Security Event Monitoring
      • Business Resiliency
        • Business Resilience Governance
        • Business Continuity Planning
        • Disaster Recovery Testing
        • Capacity Management and Redundancy
        • Backup and Recovery
      • Compliance
      • End User Device Security
      • Network Security
      • Privacy
      • Threat Management
      • Server Security
      • Cloud Hosting
Powered by GitBook
On this page
  • Web Servers
  • Verify that the web server is running on a dedicated logical system not shared with other critical applications.
  • Verify that the web server is fully patched and updated with the latest approved code.
  • Verify that unnecessary services, modules, objects, and APIs are removed or disabled. Running services and modules should be operating under the least privileged accounts.
  • Verify that only appropriate protocols and ports are allowed to access the web server.
  • Verify that accounts allowing access to the web server are managed appropriately and use strong passwords.
  • Ensure that appropriate controls exist for files, directories, and virtual directories.
  • Ensure that unnecessary information such as version and directory listings are not exposed through the web interface.
  • Ensure that the web server has appropriate logging enabled and that monitoring processes are in place.
  • Ensure that script extensions are mapped appropriately.
  • Verify the validity of any server certificates in use.
  • Web Applications
  • Ensure that the web application is protected against injection attacks.
  • Review the application for authentication and session management vulnerabilities.
  • Verify that sensitive data is identified and protected appropriately. Ensure proper use of encryption technologies to protect sensitive data.
  • Review the web server for exposure to XML external entities (XXE) attacks.
  • Verify that proper access controls are enforced.
  • Review controls surrounding maintaining a secure configuration.
  • Review the website for cross-site-scripting vulnerabilities.
  • Review protections against exploitation of deserialization sequences.
  • Review processes to ensure vulnerabilities are not present in libraries, frameworks, or other components.
  • Ensure that adequate logging is present and review processes for examining log data.
  • Review the security training provided to application development teams and ensure that development teams understand secure coding practices.
  • Verify that all input is validated prior to use by the web server.
  • Evaluate the use of proper error handling.
  • Review web application redirects and forwards to verify that only valid URLs are accessible.
  • Verify that controls are in place to prevent cross-site request forgery (CSRF or XSRF).
  1. Compliance
  2. Auditing
  3. Techniques

Auditing Web Servers and Web Applications

Web Servers

Verify that the web server is running on a dedicated logical system not shared with other critical applications.

HOW

Verify that the web server is fully patched and updated with the latest approved code.

HOW

Verify that unnecessary services, modules, objects, and APIs are removed or disabled. Running services and modules should be operating under the least privileged accounts.

HOW

Verify that only appropriate protocols and ports are allowed to access the web server.

HOW

Verify that accounts allowing access to the web server are managed appropriately and use strong passwords.

HOW

Ensure that appropriate controls exist for files, directories, and virtual directories.

HOW

Ensure that unnecessary information such as version and directory listings are not exposed through the web interface.

HOW

Ensure that the web server has appropriate logging enabled and that monitoring processes are in place.

HOW

Ensure that script extensions are mapped appropriately.

HOW

Verify the validity of any server certificates in use.

HOW

Web Applications

Ensure that the web application is protected against injection attacks.

HOW

Review the application for authentication and session management vulnerabilities.

HOW

Verify that sensitive data is identified and protected appropriately. Ensure proper use of encryption technologies to protect sensitive data.

HOW

Review the web server for exposure to XML external entities (XXE) attacks.

HOW

Verify that proper access controls are enforced.

HOW

Review controls surrounding maintaining a secure configuration.

HOW

Review the website for cross-site-scripting vulnerabilities.

HOW

Review protections against exploitation of deserialization sequences.

HOW

Review processes to ensure vulnerabilities are not present in libraries, frameworks, or other components.

HOW

Ensure that adequate logging is present and review processes for examining log data.

HOW

Review the security training provided to application development teams and ensure that development teams understand secure coding practices.

HOW

Verify that all input is validated prior to use by the web server.

HOW

Evaluate the use of proper error handling.

HOW

Review web application redirects and forwards to verify that only valid URLs are accessible.

HOW

Verify that controls are in place to prevent cross-site request forgery (CSRF or XSRF).

HOW

PreviousAuditing Cybersecurity ProgramsNextAuditing Databases

Last updated 2 years ago