www.inversecos.com Open in urlscan Pro
2a00:1450:4001:82f::2013  Public Scan

Submitted URL: http://inversecos.com/
Effective URL: https://www.inversecos.com/
Submission: On May 02 via manual from GB — Scanned from GB

Form analysis 1 forms found in the DOM

https://www.inversecos.com/search

<form action="https://www.inversecos.com/search" target="_top">
  <div class="search-input">
    <input aria-label="Search this blog" autocomplete="off" name="q" placeholder="Search this blog" value="">
  </div>
  <input class="search-action flat-button" type="submit" value="Search">
</form>

Text Content

Skip to main content


INVERSECOS






POSTS


AZURE COMMAND LINE FORENSICS - HOST BASED ARTIFACTS

 * Get link
 * Facebook
 * Twitter
 * Pinterest
 * Email
 * Other Apps

March 08, 2023

On most of the on-premises to cloud lateral movement compromises I’ve worked
relating to Azure, threat actors typically leverage a bunch of different
command-line focused tools. They use these tools to perform enumeration of the
victim’s Azure environment, backdooring active directory, various persistence
techniques and lateral movement. These are generally a combination or one of the
following (this is not a comprehensive list... just examples): AADInternals
Azure CLI AzureAD PowerShell Threat actors run these tools on servers and hosts
of interest i.e. AD FS servers, AD CS servers to abuse pass-through
authentication or abuse identity federation. The Azure CLI has also been
leveraged by attackers to perform various enumeration / reconnaissance style
attacks. If you want more detailed information around how to detect and perform
attacks against Azure and Microsoft 365, check out my " Attacking and Defending
Azure / M365 " course. High-Level Methodology First to perform t
Post a Comment


Read more


DETECTING FAKE EVENTS IN AZURE SIGN-IN LOGS

 * Get link
 * Facebook
 * Twitter
 * Pinterest
 * Email
 * Other Apps

January 10, 2023
Threat actors can create and populate fake logs in the Azure sign-in logs that
look like legitimate events The parameters they can spoof in the logs include
(and are not limited to): Timestamp of when the events are generated User
account IP addresses Network location type During forensic investigations,
analysts may not be aware that some of the logs are not “legitimate” and start
recording indicators of compromise that are not necessarily “real”. Further,
this raises the question of “trust” regarding log sources – highlighting that
during forensic investigations, it’s always best practice to utilise multiple
sources rather than solely relying on one source. This technique has previously
been written about by @DrAzureAD in his blog post here  and was also covered by
Secureworks Counter Threat Unit here . As per @DrAzureAD’s blog, this attack can
be conducted TWO ways; the second method being harder to detect than the first:
Method 1: An attacker gains local admin / domain admin
Post a Comment


Read more


HOW TO DETECT MALICIOUS OAUTH DEVICE CODE PHISHING

 * Get link
 * Facebook
 * Twitter
 * Pinterest
 * Email
 * Other Apps

December 14, 2022
  In this brilliant blog ( https://aadinternals.com/post/phishing/ ) by
@DrAzureAD, he introduced a method of phishing M365 accounts that threat actors
can leverage by abusing device code authentication. There have been a lot of
great blogs citing this technique but not much written about the detection…
which is why I am here 🙂 The reason I am writing about this technique is that
it’s significantly more difficult to detect than OAuth abuse for malicious
application registrations. The reason for this is, the entire premise of the
phish occurs within the microsoftonline.com namespace and does not redirect the
user to any third-party website and there is no need for any 3rd party
application authorization/registration. This method of phishing also bypasses
MFA requirements as the attacker gains access to the user’s refresh and access
token. I wanted to revisit this technique and blog about a detection for this
type of attack. As usual, I’ve broken this blog post into two sections: Attack
Post a Comment


Read more


RECOVERING CLEARED BROWSER HISTORY - CHROME FORENSICS

 * Get link
 * Facebook
 * Twitter
 * Pinterest
 * Email
 * Other Apps

October 25, 2022
  Hello naughty sysadmin... I've been watching your search history this Summer
O_o How do you detect when a user deletes their chrome history and is there a
way to forensically recover it? The answer is… it depends. 😈 A good indicator
for recovering what a user was doing when they deleted their chrome browser
history is by checking inside the
C:\Users\<name>\AppData\Local\Google\Chrome\User Data\Default\Sessions folder.
The two files you need to look at are named: Session_<Webkit/Chrome date>
Tabs_<Webkit/Chrome date> The session file stores session information and the
tabs file stores what tabs they had opened. In a certain situation when a user
CLEARS their Chrome history, what they were browsing can persist within these
files.  There are a few potential cases that could have occurred, and we will go
through all of them: A user cleared their history and did not use Chrome since A
user clears their history and re-opened ONE new session A user clears their
histor
Post a Comment


Read more



HOW TO INVESTIGATE INSIDER THREATS (FORENSIC METHODOLOGY)

 * Get link
 * Facebook
 * Twitter
 * Pinterest
 * Email
 * Other Apps

October 12, 2022
Insider threats are unfortunately a real and active threat. The forensic
investigation of a suspected insider follows a different approach in methodology
than the classic methodology for investigating threat actors. The main
difference between insider jobs and other jobs is the fact that clients usually
want a timeline of both activity around the “malicious action” and also a
timeline of “legitimate” activity leading up to, during and post the malicious
actions to remove reasonable doubt that it was somebody else. During an insider
job, artefacts that show system wake/hibernation, or artefacts proving a user
opened something on their taskbar are just as important as the malicious
activity itself depending on the client needs. For these cases, analysts should
*consider* create TWO timelines depending on the client needs and the nature of
the incident: One timeline for malicious activity One timeline capturing ALL
relevant activity showing what the user was actively doing since being ide
Post a Comment


Read more
More posts
Powered by Blogger


REPORT ABUSE

inversecos Visit profile


LINA LAU

lina@inversecos.com


MY CYBERSECURITY COURSE

 * XINTRA - Cybersecurity Training


MY BOOK

 * How to get a job in cybersecurity earning over six figures : Zero to Cyber
   Hero


SOCIAL

 * Twitter
 * YouTube
 * LinkedIn
 * Tiktok


SEARCH




BLOG ARCHIVE

 * March 20231
 * January 20231
 * December 20221
 * October 20222
 * September 20221
 * August 20222
 * July 20222
 * June 20223
 * May 20222
 * April 20222

 * March 20221
 * January 20221
 * December 20211
 * November 20211
 * October 20213
 * September 20212
 * May 20211
 * February 20211
 * April 20201
 * November 20191
 * March 20181
 * October 20172
 * June 20172

Show more Show less
Diese Website verwendet Cookies von Google, um Dienste anzubieten und Zugriffe
zu analysieren. Deine IP-Adresse und dein User-Agent werden zusammen mit
Messwerten zur Leistung und Sicherheit für Google freigegeben. So können
Nutzungsstatistiken generiert, Missbrauchsfälle erkannt und behoben und die
Qualität des Dienstes gewährleistet werden.Weitere InformationenOk