Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyΒ© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
InfraPulse-Core β€” A high-fidelity, read-only internal network security assessment toolkit for Linux and Windows infrastructure. Employs a zero-mutation, default-deny architecture to safely capture and structure risk telemetry without system modifications. | Kitploit
Tools/GitHubGitHub/vighnesh91/infrapulse-core
Defensive ToolsReconnaissanceVulnerability AnalysisScripting & AutomationConfiguration AuditingInformation GatheringNetwork SecurityPenetration Testing
Share
GitHubvighnesh91/infrapulse-core

InfraPulse-Core

A high-fidelity, read-only internal network security assessment toolkit for Linux and Windows infrastructure. Employs a zero-mutation, default-deny architecture to safely capture and structure risk telemetry without system modifications.

View Repository
21391 month agoNot yet reviewed

InfraPulse-Core

InfraPulse-Core is a unified, dual-platform security auditing architecture implementing single-file, zero-dependency engines for Linux (POSIX) and Windows (Win32).

Unlike traditional vulnerability scanners that rely on subjective risk metrics, InfraPulse-Core enforces an unyielding Evidence-Tuple Model, programmatically segregating static Configuration Evidence from Active Protocol Validation and Demonstrated Impact.

πŸ›‘οΈ Core Guarantees & Architectural Safeties

  1. The Single Socket Choke Point: Network egress is programmatically impossible without passing a single validation gate (socket_gate / Test-TargetAllowed). This gate evaluates the operator-supplied scope against a default-deny policy before a socket is instantiated.
  2. Zero-Mutation Footprint: The engines are strictly read-only. They do not inject processes, modify system registries, write to system binaries, harvest cleartext credentials, or execute disruptive exploits.
  3. Forensic Integrity Tracing: The very first data row of the generated CSV report computes an in-memory SHA-256 hash of the executing engine. This ties the resulting dataset explicitly to an audited codebase block.
  4. Deterministic Severity Mapping: Eliminates subjective scoring. Vulnerabilities are automatically rated based on a combination of their category class, verified runtime state, and exposure preconditions.

πŸ“ Repository Layout

InfraPulse-Core/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ posix/
β”‚   β”‚   └── InfraPulse-LX.sh      # Linux Native Bash Engine
β”‚   └── win32/
β”‚       └── InfraPulse-Win.bat    # Windows Native Extraction/PowerShell Engine
β”œβ”€β”€ LICENSE                       # MIT License terms
└── README.md                     # Main deployment guide

πŸ’» Operational Execution Modes

🟒 POSIX Audit (src/posix/InfraPulse-LX.sh)

Ensure execution permissions are granted before deployment:

chmod +x InfraPulse-LX.sh
# Execute local hardening profile with absolute network containment
./InfraPulse-LX.sh --local-only

# Execute network discovery over tightly bounded, authorised CIDR limits
./InfraPulse-LX.sh --scope 10.10.20.0/24,!10.10.20.254

πŸ”΅ WinRM & Active Directory Audit (src/win32/InfraPulse-Win.bat)

Run from an Elevated Command Prompt for maximum filesystem/LSA tracking accuracy.

:: Suppress outbound queries; audit loopback and local OS protections only
InfraPulse-Win.bat /localonly

:: Target a specific segment with an automated default-deny network stance
InfraPulse-Win.bat /scope:172.16.4.0/24,!172.16.4.10

πŸ“Š Output Artifacts

The engine splits verification tasks across two discrete files dynamically dropped into the output directory:

  • The Compliance Report (*.csv): Formatted precisely to RFC4180 rules. Tracks entries using a 14-column layout mapping: Timestamp, Severity, Category, Source, Target, Port, Finding, Prerequisites, ConfigurationEvidence, ValidationMethod, ObservedResult, Exploitability, Impact, and Remediation.
  • The Actionable Handoff (*.md): Generates an ordered, pipeline-style manual playbook. It provides the exact steps a human operator must perform to confirm or refute a vulnerability, along with a pre-calculated engineering blast radius for each check.
Download Tool

Most Popular

View all β†’

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools β†’