Skip to content

Instantly share code, notes, and snippets.

@AnasM84
AnasM84 / 20211210-TLP-WHITE_LOG4J.md
Created December 21, 2021 11:34 — forked from SwitHak/20211210-TLP-WHITE_LOG4J.md
BlueTeam CheatSheet * Log4Shell* | Last updated: 2021-12-20 2238 UTC

Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)

Errors, typos, something to say ?

  • If you want to add a link, comment or send it to me
  • Feel free to report any mistake directly below in the comment or in DM on Twitter @SwitHak

Other great resources

  • Royce Williams list sorted by vendors responses Royce List
  • Very detailed list NCSC-NL
  • The list maintained by U.S. Cybersecurity and Infrastructure Security Agency: CISA List
@AnasM84
AnasM84 / oracle-cloud-certifications-link-o-rama.md
Created December 7, 2021 00:28
Oracle Cloud Certifications - Link-O-Rama
OCI Architecture:
=================
OCI Regions - 21 Available + 15 Planned; Commercial, Govt, Microsoft Azure Interconnect
Region - Localized Geographical area comprised of 1 or more AD
Availability Domains - One or more fault-tolerent, isolated DC located within a region, but connected to each other by low latency, high bandwidth network; Do not share physical infra
Fault Domains - Grouping of hardware and infrastructure with in an AD to provide anti-affinity(logical data center); 3 FD per AD; Do not share SPOHF; change procedures are isolated at FD
One AD Regions - within one year second AD or region will be made available
Choosing Region - Location, Data Residency & Compliance, Service Availability
Avoid SPOF - Design architecture to deploy instances that perform same tasks in different FD or different AD for multiple AD regions
Data Guard - Data replication across AD

Typing vagrant from the command line will display a list of all available commands.

Be sure that you are in the same directory as the Vagrantfile when running these commands!

Creating a VM

  • vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
  • vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM

  • vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)