Phases: Covering Your Tracks: - Steganography - Event Logs Alteration
Phases: Covering Your Tracks: - Steganography - Event Logs Alteration
Phases: Covering Your Tracks: - Steganography - Event Logs Alteration
• Steganography
By-
Harshal
Sankalp
Chetan
Yashasvi
Pankaj
Covering your tracks:
An attacker needs to destroy evidence of his presence and activities
else he can get caught.
This usually starts with erasing the contaminated logins and any possible
error message that may have been generated from the attack process.
It is imperative for attacker to make the system look like it did before
they gained access and established backdoors for their use.
Trojans such as netcat comes in handy for any attacker who wants
to destroy the evidence from the log files or replace the system
binaries with the same.
An attacker can use the system as a cover to launch fresh attacks against other
system or use it as a means of reaching another system on the network without
being detected.
In modern digital steganography, data is first encrypted by the usual means and
then inserted, using a special algorithm, into redundant data that is a part of a
particular file format such a JPEG image.
Event Logs Alteration:
A log file is a file that records either events that occur in an
operating system or other software runs or messages between
different users of a communication software. Logging is the act of
keeping a log. In the simplest case, messages are written to a single
log file.
Event that are written to the application log are determined by the
Security log: -
The security log contains events such as valid and invalid logon attempts. It
also contain events that are related to resource use, e.g. when you create,
administrative group to turn on, to use, and to specify which events are
The system log contains events that are logged by windows system
The Directory Service log contain Active Directory-related events. This log is
The DNS Server log contain events that are related to the resolution of DNS
The File Replication Service log contains events that are logged during
the replication process between domain controllers.
By default, Event Viewer log file use the .evt extension and are located
in the ‘%SystemRoot%\System32\Config’ folder.
Log file name and location information is stored in the registry. You can
edit this information to change the default location of log files.
ANY QUERIES?