PowerShell module to check Windows binaries for security features like ASLR, DEP, SafeSEH, and Authenticode.
PESecurity is a PowerShell module that checks Windows executable files (EXE/DLL) for security mitigations like ASLR, DEP, SafeSEH, StrongNaming, Authenticode, Control Flow Guard, and HighEntropyVA. It helps security professionals quickly assess the security posture of binaries across Windows systems. The tool can scan individual files or entire directories recursively and export results for further analysis.
Windows security professionals, penetration testers, system administrators, and blue team members who need to assess binary security hardening across enterprise environments.
PESecurity provides a lightweight, PowerShell-native solution for binary security analysis that integrates seamlessly into existing Windows workflows, unlike heavier standalone tools or manual inspection methods.
PowerShell module to check if a Windows binary (EXE/DLL) has been compiled with ASLR, DEP, SafeSEH, StrongNaming, and Authenticode.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Checks for key Windows security features including ASLR, DEP, SafeSEH, Control Flow Guard, and HighEntropyVA, as listed in the feature set, providing a comprehensive security snapshot.
Supports recursive directory scans for multiple files, enabling large-scale assessments with commands like 'Get-PESecurity -directory C:\Windows\System32\ -recursive'.
As a PowerShell module, it seamlessly fits into existing Windows automation workflows, allowing easy scripting and pipeline integration, as shown in the import and usage examples.
Allows exporting results to CSV and formatting in tables, facilitating data analysis and reporting, as demonstrated with 'Export-CSV' and 'Format-Table' commands.
Exclusively analyzes Windows EXE/DLL files and requires a PowerShell environment on Windows, making it unsuitable for cross-platform security assessments.
Performs only static checks on compiled binaries without runtime behavior analysis, which may miss dynamic security vulnerabilities or evasion techniques.
Limited to a predefined list of mitigations and may not support newer or custom security mechanisms without code updates, as indicated by the lack of extensibility mentions.