Internal Penetration Test

By Ashwin Venugopal -

 






Introduction

An internal penetration test is generally done after the completion of an external pen test. It imitates an insider threat and identifies the ways an attacker can compromise or damage the network, sensitive data, or systems. Initially, the tester may start with the most obvious or common scenarios like:
  1. An unhappy rogue employee (malicious insider) who can compromise or damage the system network.
  2. An external malicious attacker who accesses the system through social engineering, phishing scam, or stolen credentials. 

Mostly, organizations on external threats but, it has been proved that a majority of data breaches happens dur to internal threats and they can come from-

  1. Weak or shared passwords
  2. Weak access controls
  3. Insecure file sharing or unencrypted data
  4. Network misconfigurations
  5. Lack of awareness about social engineering and phishing
  6. Ransomware attacks
  7. Insecure remote devices and networks

It is very important to address these issues on priority and internal penetration testing does just that.

Internal Discovery

Firstly, a penetration tester try to look for other hosts. Hence, according to the noise he wants to make, he might use the tools, like netdiscover, that do not generate much noise or traffic in the network so he can stay undetected. A penetration tester needs to be undetected and discreet but, it's quite a difficult feat to achieve once inside the network. However, following techniques might help the tester i these aspects:
  • TTL Manipulation- Sending some packets with a TTL long enough to reach the IDS (Intrusion Detection Systems) or IPS (Intrusion Prevention Systems) but not long enough to reach the target system. After that, send some more packets with same sequences so that the IPS/IDS mistake them for repeats and fail to inspect them even if they contain malicious material. This can done through nmap's (ttlvalue parameter).

  • Avoid Signatures- In order to avoid getting caught with a known malicious signature, nonces or garbage data to the packets. This can be achieved with the help of nmap's (data-length parameter).

  • Fragmented  Packets- This is a very successful technique. Just split the packets and send them apart so that any IDS/IPS they come across will reassemble these packets and realize that they are malicious ones. It can be done via nmap's (-f parameter).

  • Invalid Checksum- For this to work properly, the IDS/IPS should either not be setup to handle invalid checksums or be misconfigured. 

  • Uncommon IP and TCP Options- The target host might accept the packet immediately after reception, a sensor may ignore packets with certain flags and options specified inside the IP and TCP headers.

  • Overlapping- While fragmenting the packets, some of the bytes between different packets might overlap. This makes it difficult for IDS/IPS to reassemble them and leads to misinterpretation of the packets in different ways than the destined host. 

Conclusion:

In this part we discussed in more detail about the Internal Penetration Testing and its techniques.




















































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more