updated documentation for #2448 - PE Analyzer

src/site/markdown/analyzers/assembly-analyzer.md

@@ -7,7 +7,6 @@ is internally referred to as evidence and is grouped into vendor, product, and v
 buckets. Other analyzers later use this evidence to identify any Common Platform
 Enumeration (CPE) identifiers that apply.
 
-If dependency-check is being run on a linux system `mono-runtime` and `mono-devel` needs to be
-installed for this analyzer to work.
+.NET core 2.x needs to be installed for this analyzer to work.
 
 Files Types Scanned: EXE, DLL

src/site/markdown/analyzers/index.md

@@ -34,6 +34,7 @@ several teams have found them useful in their current state.
 | [Composer Lock](./composer-lock.html) | PHP [Composer](http://getcomposer.org) Lock files (composer.lock) | Parses PHP [Composer](http://getcomposer.org) lock files for exact versions of dependencies. | 
 | [Go lang mod](./golang-mod.html) | `go.mod`| Uses `go mod` to determine exactly which dependencies are used. |
 | [Go lang dep](./golang-dep.html) | `Gopkg.lock` | Analyzes the lock file directly to parse dependency information. | 
+| [PE Analyzer](./pe-analyzer.html) | `PE DLL and EXE` | Analyzes the PE Headers to obtain dependency information. | 
 | [Python](./python.html) | Python source files (\*.py); Package metadata files (PKG-INFO, METADATA); Package Distribution Files (\*.whl, \*.egg, \*.zip) | Regex scan of Python source files for setuptools metadata; Parse RFC822 header format for metadata in all other artifacts. |
 | [Ruby Gemspec](./ruby-gemspec.html) | Ruby makefiles (Rakefile); Ruby Gemspec files (\*.gemspec) | Regex scan Gemspec initialization blocks for metadata. |
 | [SWIFT](./swift.html) | SWIFT Package Manager's `Package.swift` | Extracts dependency information from swift package file. |

src/site/markdown/analyzers/pe-analyzer.md

@@ -0,0 +1,10 @@
+PE Analyzer
+==============
+
+OWASP dependency-check includes an analyzer that scans PE dll and exe files and 
+collect as much information it can about the files as it can. The information collected
+from the PE headers and is internally referred to as evidence and is grouped into vendor,
+product, and version buckets. Other analyzers later use this evidence to identify any
+Common Platform Enumeration (CPE) identifiers that apply.
+
+Files Types Scanned: EXE, DLL