Infrastructure Penetration Testing
We’re the good hackers for hire.
Perimeter infrastructure isn’t as porous as it used to be. In our experience, most infrastructure security threats stem from misconfiguration and human oversight. Automated testing cannot find these common errors. Our veteran engineers have you covered.
We start by understanding your systems. A security engineer identifies and fingerprints live hosts, and starts probing. What is the network topology? Which operating systems and available services are present? Are access control mechanisms in place? What core interactions occur between systems?
Using known vulnerabilities, a security engineer attempts to find entry points. Known vulnerabilities include legitimately provided services such as HTTP, FTP, SMTP mail exchangers, DNS, IMAP/POP, and file sharing services.
What vulnerabilities are present? These relate to network components configuration, design principles, and protocol-specific characteristics. Testing for these vulnerabilities utilizes spoofing techniques and protocol specific tests. A security engineer may exploit fragmentation, trust relationships, protocol encapsulation, routing tricks, and implementation flaws.
Misconfiguration and Backdoor Tests
Are systems configured correctly? Are there any backdoors? A security engineer attempts to exploit both.
Authentication and Access Control Schemes
Can a security engineer subvert authentication and access control mechanisms? They might use dictionary and brute force attacks on reusable passwords. They can exploit authentication schemes, social engineering, and contingency plan procedures.
White Box, Black Box, or a Combo
Our infrastructure penetration testing services include white, black, or gray box methodologies.
Recent Blog Posts
Rewrite: Justin Fimlaid Original Author: Hunter Gregal Cross-site scripting, or otherwise known as XSS, is the most common web application vulnerability on the internet. I have found this to be true through both data research and personal experience during penetration...
By: Randy Duprey What is Red Teaming? Red teaming in general can be defined as a goal-based adversarial testing process. The concept has existed since the sixth Century BCE when the ancient military genius Sun Tzu stated that "…one who knows the enemy and knows...
“NuHarbor performed an internal penetration test of our organization. Utilizing one of our legacy network protocols, they were able to gain administrative acces and push malicious code to our network. Had this been a real attack, we could have lost everything.”
External Penetration Testing
We test the security posture and presentation of your external infrastructure facing the internet. We offer white box, black box, or a combination methodology. In white box testing, you provide architecture details of the technology being tested. With black box methodology, we begin with no information about your architecture. This simulates a nefarious outsider probing your company for weak points. In a gray box or hybrid solution, we start with no knowledge and move towards full knowledge to ensure thorough coverage. This is often the best use of clients’ budgets because you receive the best coverage for your time investment.
Internal Penetration Testing
We test the security posture of your internal infrastructure. As part of this test effort, we assess what someone within your internal network might be able to access. Think about the many clients, partners, and employees in your office. Where are you most vulnerable? For example, we can test as an outsider by connecting to the network port in a vacant conference room. Alternatively, you could provide logins for us to operate as a trusted insider to measure your security exposure.