• Penetration Testing

    Every penetration test is different. Depending upon the goals of the organization and engagement, a penetration test can take anywhere from a few hours to hundreds of hours. Securit360 performs tests following The Penetration Testing Execution Standard (www.penetration-test.org), and supplements with other methods from 1) The Open Source Security Testing Methodology Manual (OSSTMM), 2) Open Web Application Security Project (OWASP), 3) the Penetration Testing Framework (PTF) as well as our own experience and understanding which is then tailored to the specific needs of the client and engagement. We have an arsenal of tools and methods to use as the test develops.

    We offer penetration testing for both internal and external networks.  Each type of test is slightly different.  In an external test our main two goals are to gain access to the internal network or to discover information that should not be available from the outside.  In an internal penetration test we are trying to learn the layout of the network, identify high value targets, gain access to systems and exfiltrate sensitive data.

    Physical and Social Engineering

    We can make multiple social engineering attempts as well attempts to exploit the physical perimeter.  We will work with a client to see what works best considering the organization and usually include taligaiting, presentation of false credentials and impersonation of key employees.

    Assessment Procedures
    1. Information Gathering
    2. Configure Penetration Testing Software
    3. Testing to insure accurate results
    4. Schedule Assessments to minimize impact to productivity
    5. Test web applications with software as well as with manual test
    6. Compare assessment reports to IT inventory for analysis
    7. Issue report and analysis
The OWASP top 10

The Open Web Application Security Project (OWASP) Top Ten provides a powerful awareness document for web application security. The OWASP Top Ten represents a broad consensus about what the most critical web application security flaws are. Project members include a variety of security experts from around the world who have shared their expertise to produce this list.


Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.

Broken Authentication and Session Management

Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.

Cross-Site Scripting (XSS)

XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

Insecure Direct Object References

A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.

Security Misconfiguration

Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

Sensitive Data Exposure

Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

Missing Function Level Access Control

Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

Cross Site Request Forgery (CSRF)

A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim

Using Components With Known Vulnerabilities

Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts

Unvalidated Redirects and Forwards

Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.