Downloads of v 2.9.1:


Last Update:

16 Jan 2017

Package Maintainer(s):

Software Author(s):

  • Trustwave SpiderLabs


modsecurity iis

modsecurity (Install)

2.9.1 | Updated: 16 Jan 2017



Downloads of v 2.9.1:



Software Author(s):

  • Trustwave SpiderLabs

modsecurity (Install) 2.9.1

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install modsecurity (Install), run the following command from the command line or from PowerShell:


To upgrade modsecurity (Install), run the following command from the command line or from PowerShell:


To uninstall modsecurity (Install), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade modsecurity -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade modsecurity -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure modsecurity installed
    name: modsecurity
    state: present
    version: 2.9.1
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'modsecurity' do
  action    :install
  version  '2.9.1'
  source   'STEP 3 URL'

See docs at

    Name: modsecurity,
    Version: 2.9.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller modsecurity
   Name     = 'modsecurity'
   Ensure   = 'Present'
   Version  = '2.9.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'modsecurity':
  provider => 'chocolatey',
  ensure   => '2.9.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install modsecurity version="2.9.1" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator flcdrg on 30 Jan 2017.


ModSecurity is an open source, cross platform web application firewall (WAF) developed by Trustwave's SpiderLabs. It has a robust event-based programming language which provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring, logging and real-time analysis. With over 10,000 deployments world-wide, ModSecurity is the most widely deployed WAF in existence.

$ErrorActionPreference = 'Stop';
$packageName= 'modsecurity'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$url64      = ''

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'MSI'
  url           = $url
  url64bit      = $url64

  softwareName  = 'modsecurity*'

  checksum      = 'bd9c75bd8975c89cc7000679fc4bcee62d7594d36070f9b5ea75b283edf6fac7'
  checksumType  = 'sha256'
  checksum64    = '7ef38c203e97ef5708b06718e46f54239eaf04c27031d40efb39a57bcf2a92f1'
  checksumType64= 'sha256'

  silentArgs    = "/quiet /norestart /l*v `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`""
  validExitCodes= @(0, 3010, 1641)

# Detect if IIS is enabled. We need this to be enabled before installing modsecurity.
if(!(test-path "$env:systemroot\system32\inetsrv\Microsoft.Web.Administration.dll")) {

    $dism = "$env:WinDir\System32\dism.exe"
    # Add Windows Feature IIS Webserver
    Write-Host "Enabling Windows Feature: IIS Webserver"

    $iisArgs = "/Online /NoRestart /Enable-Feature /All /FeatureName:IIS-WebServer"
    #$statements = "$dism $iisArgs"
    Start-ChocolateyProcessAsAdmin -Statements "$iisArgs" -minimized -nosleep -validExitCodes @(0,1) -ExeToRun $dism

Install-ChocolateyPackage @packageArgs

# Configure IIS (Unlock ModSecurity sections so that it can actually be configured).
# This is optional, so in a try-catch.
try {
    $assembly = [System.Reflection.Assembly]::LoadFrom("$env:systemroot\system32\inetsrv\Microsoft.Web.Administration.dll")
    $manager = new-object Microsoft.Web.Administration.ServerManager
    # load appHost config
    $config = $manager.GetApplicationHostConfiguration()

    Write-Host "Unlocking system.webServer/ModSecurity"
    $section = $config.GetSection('system.webServer/ModSecurity')
    $section.OverrideMode = 'Allow'
    Write-Host "Unlocked system.webServer/ModSecurity"
catch { } 

#Download OWASP ModSecurity Rules
$rulesetPath =  "$env:ProgramData\ModSecurity"
$rulesetChecksum = "1090D5A67B88A99D093211C604B271821BADADBAC13F6E50B214DE2F6D46194F";
Install-ChocolateyZipPackage -PackageName 'owasp-crs' -Url '' -UnzipLocation $rulesetPath -Checksum $rulesetChecksum -ChecksumType sha256

$ErrorActionPreference = 'Stop';

$packageName = 'modsecurity'
$softwareName = 'modsecurity*'
$installerType = 'MSI' 

$silentArgs = '/quiet /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the modsecurity (Install) Package

Ground Rules:

  • This discussion is only about modsecurity (Install) and the modsecurity (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or modsecurity (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus