sathishphcl

# CopyManagedDisk.ps1
# Morgan Simonsen
# morgansimonsen.com
#
# Copies an Azure managed disk from one Azure region to another via a storage account

[CmdletBinding()]
Param(
  [Parameter(Mandatory=$True,Position=1,
  HelpMessage="Source resource group where the managed disk(s) to copy is.")]

sathishphcl

---
- hosts: localhost
  become: True
  vars:
    archive_path: /home/vagrant/containers
    containers:
      - name: quay.io/dcode/strelka_manager
        tag: latest
        id: 8b8321cf9c81
      - name: quay.io/dcode/strelka_frontend

sathishphcl

# Copyright 2019, Alexander Hass
# https://www.hass.de/content/setup-microsoft-windows-or-iis-ssl-perfect-forward-secrecy-and-tls-12
#
# After running this script the computer only supports:
# - TLS 1.2
#
# Version 3.0.1, see CHANGELOG.txt for changes.
 
Write-Host 'Configuring IIS with SSL/TLS Deployment Best Practices...'
Write-Host '--------------------------------------------------------------------------------'

sathishphcl

#Security log
#============
####
#4624 - Logon & Logoff events successful
#4625 - Logon unsucceful

####
# Get usernames
Get-WinEvent -path .\Security.evtx | Where {$_.id -eq "4624"} | Foreach {([xml]$_.ToXml()).GetElementsByTagName("Data").ItemOf(5)}| Select -ExpandProperty "#text" -Unique 
# Get domains

sathishphcl

using namespace Microsoft.Azure.Commands.ResourceManager.Common.ArgumentCompleters

function Invoke-AzVMScript {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory)]
        [ResourceGroupCompleter()]
        [string]$ResourceGroupName,

        [Parameter(Mandatory)]

sathishphcl

Purpose

*Most pentesting and gcp privilege escalation stuff out there for GCP assumes what I'm finding to be an absurd level of access handed to you.(i.e Human 2fa protected accounts, organization-wide read only IAM perms, etc that is not suitable for use in black box testing of mature environments.
There's a lot of data you need to use the gcp api only available behind mandatory 2fa protected human accounts that service accounts and low tier project accounts simply do not have access to enumerating if you find yourself having popped an application or shelled a instance somehow and have console-only access.

Intent of this is to break down various categories of escalation that will be available to service accounts, as well as point out various showstoppers.

• 0.1. References
• 0.2. Other cheatsheets
• 0.3. Manage multiple gcloud config configurations
• [0.3.1. Switch gcloud context with gcloud config](#031

sathishphcl

gcloud config set compute/zone us-east1-b
gcloud container clusters create nucleus-jumphost-webserver1
gcloud container clusters get-credentials nucleus-jumphost-webserver1
kubectl create deployment hello-app --image=gcr.io/google-samples/hello-app:2.0
kubectl expose deployment hello-app --type=LoadBalancer --port 8080
kubectl get service

cat << EOF > startup.sh
#! /bin/bash
apt-get update

sathishphcl

Organization archetypes

The intention of this document is to provide some guidance and suggestions to customers who are wondering how they should structure organizations and teams in their GitHub Enterprise environment. The idea isn't to give hard and fast rules on which approach is better than the other, but to give examples of when one approach might be preferable to another depending on the use case.

1. A single organization with direct organization membership for repository access (not teams)

          ________________
          |     Org      |
          |    ______    |
          |   |      |\  |

| | Repo | \ |

sathishphcl

<#
    .SYNOPSIS
        This script:
        Creates a new resource group
        Creates a VNet with two subnets in the RG
        Allocates a static public IP
        Creates a NSG and adds rules permitting TCP 3389, 80 and 443
        Launches a WinSrv2012R2 instance
        Configures RDG server via Remote Desktop Services PowerShell provider using a DSC configuration
        The DSC configuration:

sathishphcl

<# 
.SYNOPSIS 
    Migrates a Azure Virtual Machine to another subscription or data centre

.DESCRIPTION 
    Shutsdown the source VM
    Exports the VM config to a temporary file
    Loops through all Azure disks attached to the source VM
    Schedules an async copy of the underlying VHD to the destination storage account
        - optionally overwrites existing VHD in destination if it exists