Network Penetration Testing

Each Penetration Test is performed by one of Securisea’s experienced professionals, and is customized for each customer to ensure accuracy and safety. The result from each test is a detailed report analyzing how an intruder might gain access to internal systems under specific conditions, and the necessary steps to prevent such an intrusion in the future.

One of the key advantages to Securisea’s Penetration Testing program is our deep knowledge of both information security infrastructure and industry-specific regulatory requirements. We regularly perform Penetration Tests that assess general network security preparedness, as well as regulation-specific tests that directly evaluate compliance with PCI, FedRAMP, HIPAA and much more.

‍Securisea’s penetration-testing methodology is based on components from NIST SP800-115, the Penetration Testing Execution Standard (PTES), and the Open Web Application Security Project (OWASP) Top 10. Securisea maintains a separate, detailed penetration testing methodology document that is available upon request.

At the conclusion of our engagement, Securisea will provide you with the following deliverables: An Executive Summary tailored to your management management that provides a high-level summary of the work performed and the key findings and recommendations. A key findings section outlining the assessment activities and documenting the detailed technical findings. Attacker tactics, techniques, and processes are mapped back to the MITRE ATT&CK framework. Audit-ready reports that can be used for compliance audits that require security testing, such as PCI-DSS and HIPAA (add all, include language around as long as they are requested/in scope. FedRamp, StateRamp). These reports have been designed with compliance reporting requirements in mind.

Securisea employs our custom AWS-centric methodology for penetration testing of your cloud resources. We have extensive experience performing network level penetration testing of EC2 virtual servers as well as container based execution environments such as Elastic Container Service (ECS), including containers running within Fargate as well as Elastic Kubernetes Service (EKS) and nearly any other AWS deployment model.