What is Network Security Testing?

In our penetration testing methodology, we follow a meticulously designed process for identifying and prioritizing the most vulnerable parts of your network. Accordingly, we recommend actionable solutions to our clients. The chief objective of running a network penetration test is to identify exploitable vulnerabilities in networks, network devices, systems, and hosts so that such vulnerabilities are fixed before any hacker can detect and misuse them.

Network penetration testing helps in detecting critical vulnerabilities that can potentially enable hackers to compromise systems, gain unauthorized access to sensitive data and even take over systems for malicious purposes.

Talk To a Security Expert

We Will Help You To Choose The Best Plan!

Message Submitted!

Network Penetration Testing Methodology

Each network penetration test conducted by Kratikal involves the use of globally accepted and industry-standard frameworks. At a minimum, the underlying framework is based on the Penetration Testing Execution Standard (PTES) and National Institute of Standards and Technology (NIST) and goes way beyond the initial framework itself.

This involves the analysis of vulnerabilities, which includes analyzing the output from various security tools and manual testing techniques. A network vulnerability assessment consists of a broad range of tasks, such as:

CERT-In Certification
CERT-In Logo

Kratikal is now empanelled by CERT-In

Kratikal provides a complete suite of Customizable Security Auditing Services.

We Comply with all the Top IT Security Testing Guidelines

CERT
CISBenchmarks
CWE
hipaa
nist
OWASP
OWASP
Sans

Wireless VAPT Methodology

After the initiation of the project, target information will be given by the client. In cases of wireless penetration testing, the collected information will consist of a list of all SSIDs and MAC Addresses in scope. This information assists the Tester in finding out which access points are accounted for and which ones are rogue access points. In addition, at this stage of testing, a list of all the locations and buildings is collected before the project is scheduled.

  1. Site Survey
  2. Unauthorized Access Attempts
  3. Post-Authentication

Once our assessment is complete, we deliver a detailed network analysis and executive summary that includes effective remediation steps. We strive to provide clear and concise reports that include the following:

  • Executive Summary
  • Identified Vulnerabilities and Risk Ratings
  • Detailed Risk Remediation Steps

Configuration Auditing Methodology

The purpose of this methodology is to evaluate the security of an organization’s systems using the security audit to identify vulnerabilities in the systems. Our auditing methodology goes beyond the detection process of simple scanning software. We identify and prioritize the most vulnerable areas of your network and recommend actionable solutions.

After initiating the project, scoping/target information will be collected from the client. In the case of a Windows/ Linux/another type of server configuration review, this information will include:

  • IP Addresses of the Systems/Servers in scope
  • Read-Only Administrator-level credentials (we want to see all configuration settings without the ability to modify)
  • Any required access information (e.g., we will need VPN credentials to your internal network before we can access it)

Planning / Execution

  1. Check for Server Message Block Memory Corruption Vulnerability
  2. Check for Bluekeep Vulnerability
  3. Check for drive encryption
  4. Check for network security
  5. Check for access control
  6. Check for user rights assignment
  7. Check for user account policies
  8. Check for auditing and logging

Windows-Based System Config
Audit Test Cases

  1. Check for is Kernel vulnerable to Dirty Cow
  2. Check for System Vulnerable to Spectre and Meltdown
  3. Check for Sudo Security Bypass.
  4. Check for iptables rules if defined or not
  5. Check for kernel version if vulnerable or not
  6. Check for User can Access log files or not
  7. Check for Security-Enhanced Linux (SELinux)
  8. Check User Directory Permission not limited to user's directory itself

Linux-based System Config
Audit Test Case

  1. Turn Off the SQL Server Browser Service
  2. Check for Use Groups and Roles to Simplify Management of Effective Permissions
  3. Check for Principle of Least Privilege when Assigning SQL Server Roles
  4. Check for Strong Passwords for Database Administrators
  5. Check for Install SQL Server Updates Promptly.
  6. Check for Appropriate Authentication Options
  7. Check for Control Password Options for Logins
  8. Check for a Strong Database Backup Strategy

SQL Database Config
Audit Test Case

Firewall Auditing Methodology

After initiating the project, scoping/target information will be collected from the client. In the case of a firewall configuration review, this information will include:

  • IP Addresses and/or URLs for the firewalls in scope
  • Read-Only Administrator-level credentials
  • Any required access information (e.g., we will need VPN credentials to your internal network before we can access it)

Planning / Execution

Security Configuration Review

The second major portion of this type of assessment is the access control list (ACL) review. Our engineers will evaluate your rules from a best practice perspective, highlighting dangerous or risky rules, potential misconfigurations, overly permissive rules, etc. This will consider your organization’s business needs, where possible, and detail administrative improvements that can be made in how your team is managing the target devices. Things like proper object creation, duplicate objects/rules, poorly documented rules, unused object/rules, and temporary rules can be just as dangerous to your security posture over time.

Firewall Rule-Set Review

  1. Check for any allowed policy rule with any source/destination interface and port.
  2. Check for any allowed policy rule with any source and destination.
  3. Check for Security Profiles implementation on policies.
  4. Check for Secure Management protocols usage for access.
  5. Check for insecure services enabled on the device.
  6. Check for unused interfaces on the device.
  7. Check for authentication mechanism on the device.
  8. Check for trusted host’s access.

Firewall Auditing Test Case

Reporting

Router Auditing Methodology

After initiating the project, scoping/target information will be collected from the client. In the case of a router configuration review, this information will include:

  • Configuration files of routers in scope
  • Any additional requirements

Planning / Execution

Security Configuration Review

  1. Check for External AAA Server being used for User Authentication
  2. Check for authentication mechanism
  3. Check for management access
  4. Check for SNMP access configuration
  5. Check for access control on interfaces
  6. Check for default credentials
  7. Check for password encryption
  8. Check for trusted host’s access

Router Auditing Test Cases

Reporting

BYOD Configuration Methodology

The scope of this section is limited to configuring and reviewing the onboarding process of BYOD. It assumes that the BYOD onboarding process (e.g., ISE) is already up and running, configured with certificates, and integrated with Active Directory

After initiating the project, scoping/target information will be collected from the client. In the case of a BYOD configuration review, this information will include:

  • All the device information in scope
  • Any additional requirements

Planning / Execution

Security Configuration Review

  1. Check for Specify power-on password to log on to the device.
  2. Check for what data can be accessed remotely.
  3. Check for device is up to date or not.
  4. Check if device backups are Encrypted or not.
  5. Check if the device is jailbroken/rooted.
  6. Check for installed /banned applications.
  7. Check for a FaceID or passcode.
  8. Check “Erase all data before return, repair, or recycle functionality” enable or not.

BYOD Auditing Test Case

Reporting

Tools Used

We use industry benchmark security testing tools across each of the IT infrastructure as per the business and technical requirements.
Below are few from many of the tools we use:

Burpsuite

Nipper

Nmap

Nikto

Metasploit

OpenVAS

Aircrack-ng

Wireshark

John the Ripper

What Our Clients Say About Us?

Frequently Asked Questions

Browse through the FAQs given below to find answers to the commonly raised questions related to the VAPT services

While conducting internal network VAPT, an external assessment is carried out first to make sure that there is no data leakage externally. Once done, we require access to the internal network through a VPN to carry out a further assessment and device-level analysis.
Network VAPT is carried out in accordance with the guidelines of NIST SP800-115, PTES, CIS Benchmarks.
Besides periodic VAPT, it is also advisable to perform device-level security analysis along with configuration audit as per OEM’s recommended security policies and procedures.
It is highly recommended to carry out VAPT once every 6 months to identify any potential network intrusions and gaps.

Trusted By

Some of our valuable customers who have partnered with us.