What is Network Security Testing?

Network testing is a method of evaluating the current state security of the Network including internal, external security assessment and device-level security policies throughout a network to detect and illustrate flaws and assess hazards.

At Kratikal, we use a precisely planned procedure for identifying and prioritizing the most susceptible elements of your network in our penetration testing methodology. A network penetration test's main goal is to find exploitable vulnerabilities in networks, network devices, systems, and hosts so that they may be corrected before a hacker can discover and exploit them.

Talk To a Security Expert

We Will Help You To Choose The Best Plan!

Message Submitted!

Network Penetration Testing Methodology

Kratikal employs globally approved and industry-standard frameworks in each network penetration test it does. The structure is based on the industry standard guidelines like Penetration Testing Execution Standard (PTES) and the National Institute of Standards and Technology (NIST) at a minimum, but it goes well beyond that.

This entails vulnerability analysis, which includes examining the output of various security tools as well as manual testing procedures. A network vulnerability assessment entails a variety of tasks like –

  • Threats to the network must be identified, prioritized, and quantified
  • Checks for security control
  • Analyzing network defenses against network-based assaults such as local privilege attacks, network intrusion, port scanning, and brute-force attacks, among others.
CERT-In Certification
CERT-In Logo

Kratikal is a CERT-In Empanelled Security Auditor

We Comply with all the Top IT Security Testing Guidelines


Wireless VAPT Methodology

The client will provide target information after the project is launched. In the case of wireless penetration testing, the information gathered will include a list of all SSIDs and MAC Addresses that are in scope. In addition, before the project is scheduled, a list of all the places and structures is compiled at this stage of testing.

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

We give a full network analysis and executive summary with appropriate remediation measures when our assessment is completed. We strive to offer reports that are clear and simple and include the following information:

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

Configuration Auditing Methodology

The goal of this methodology is to use a security audit to assess the security of an organization’s network devices and find weaknesses. The detection technique of simple scanning software isn't enough for our auditing methodology. We identify and prioritize your network's most vulnerable locations, as well as provide actionable recommendations.

The client's scoping/target information will be obtained after the project is launched. This information will be included in a Windows/ Linux/other type of server configuration review:

  • IP Addresses of the systems/ Servers in scope
  • Read only Administrator- level Credentials (All configured settings without the ability to modify)
  • Any required access information (E.g. – VPN credentials)

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

The client's scoping/target information will be obtained after the project is launched. This information will be included in a firewall setup review:

  • IP Addresses and URLs for the firewalls in scope
  • Read Only Administrator-level credentials
  • Any required access information (E.g. – VPN credentials)

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


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


BYOD Configuration Methodology

The purpose of this methodology is to configure and review the BYOD onboarding procedure. It is assumed that the BYOD onboarding process (for example, ISE) is already up and running, with certificates configured and Active Directory integrated.

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


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:









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

How is internal network VAPT carried out?

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.

What are the industry guidelines for Network VAPT?

Network VAPT is carried out in accordance with the guidelines of NIST SP800-115, PTES, CIS Benchmarks.

What is important for network security besides VAPT?

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.

How frequently should VAPT be carried out?

It is highly recommended to carry out VAPT once every 6 months to identify any potential network intrusions and gaps.

How can I Help you

[email protected]

Trusted By

Some of our valuable customers who have partnered with us.