Persistence (Part 1)

By Ashwin Venugopal -

 






Overview

Deploying persistence by a penetration tester is important during penetration testing assessment. Hence, implementing persistence throughout the AD compromise process, the tester can ensure that his access cannot easily be revoked by the blue team. 

Credentials

It is one of the most common but least reliable persistence techniques. DC sync is a process in which AD DC exchange updates and replicate data with each other. Each DC runs a Knowledge Consistency Checker (KCC) that generates a replication topology for the AD forest. Also, it automatically connects to other domain controllers via Remote Procedure Calls (RPC) to synchronize information. It contains updated information like the user's new password and new objects such as when a new user is created. DC sync attack is very popular. If the penetration tester has access to an account that has domain replication permissions, he can stage a DC Sync attack to harvest credentials from a DC.

Tickets

Golden Ticket

AD environments are the target of golden ticket attacks, a subset of advanced persistent threat (APT) attacks. By generating a fake Kerberos ticket, a penetration tester can utilize them to enter a domain without authorization and stay active on the network. A ticket for Kerberos is a digital token that a DC issues to a user or service account so they can use it to log in and access domain resources. Golden tickets are used to authenticate users in an AD environment by taking advantage of the way Kerberos tickets are issued.

After obtaining the golden ticket, the penetration tester can use it to authenticate as any user inside the domain and gain access to all resources, including private information and vital systems, that the account is permitted to access. This can allow the attacker to remain undetected while moving laterally around the network, exfiltrating data or delivering malicious payloads. Since golden tickets look just like real Kerberos tickets, they can be challenging to identify.

Silver Ticket

Similar to golden tickets, silver tickets are a kind of APT assault. A penetration tester can generate a fake Kerberos service ticket called a "silver ticket" by utilizing the encryption key, service account name, and Service Principal Name (SPN) from a compromised service account. Using this knowledge, the penetration tester can fabricate a new service ticket with fictitious data that appears just like a genuine service ticket.
 
After obtaining the silver ticket, the penetration tester can use it to access any resources that the service account is permitted to access and authenticate to a particular service, such as a file server, web server, or terminal server. This will allow him to navigate the network laterally while staying undetected. Silver tickets are also hard to identify.

Certificates

The penetration tester requires a valid certificate for client authentication. It will allow him to use the certificate to request a TGT. This way he can continue to order TGTs irrespective of the number of rotations they do on the account being attacked. He can only be kicked out if he himself revoke the certificate he generated or it expires. This means, he will have persistent access for roughly next 5 years, by default.

Stealing the private key of the root CA's certificate is another way to generate certificates on demand. Since these certificates are not issued by the CA, the blue team cannot revoke them. This will mean the rotation of CA, i.e., all the issued certificates should be revoked to kick the penetration tester out. 

These techniques are incredibly invasive and hard to remove. Even the penetration tester has to signoff on his red team exercise to perform these techniques. Mostly, the red team exercise will be dechained instead of using them. Hence, most likely these persistence techniques are not to be performed but rather simulated. 

Conclusion

This part talks about the various persistence techniques and usages. 



















































Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more