|
@@ -0,0 +1,37 @@
|
|
|
+---
|
|
|
+title: Fatclient Audits
|
|
|
+categories: [cheatsheets]
|
|
|
+tags: [fatclient, reversing]
|
|
|
+---
|
|
|
+
|
|
|
+# Fatclient Audits
|
|
|
+
|
|
|
+* Architecture
|
|
|
+* Methodology
|
|
|
+ - Information Gathering
|
|
|
+* Proxying Fatclients
|
|
|
+* Analysing Custom Protocols
|
|
|
+* .NET
|
|
|
+* Java
|
|
|
+*
|
|
|
+
|
|
|
+
|
|
|
+## Architecture
|
|
|
+
|
|
|
+* Two-Tier Architecture
|
|
|
+* Three-Tier Architecture
|
|
|
+
|
|
|
+### Two-Tier Architecture
|
|
|
+
|
|
|
+Classic Client-Server Architecture. Client directly communicates with e.g. Backend/Sql/... Server.
|
|
|
+
|
|
|
+### Three-Tier Architecture
|
|
|
+
|
|
|
+In this architecture the client communicates with an application server using an API (mostly HTTP/s).
|
|
|
+The application server then communicates to e.g. the database.
|
|
|
+
|
|
|
+-> This is more secure as the DB is not accessed directly.
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+#
|