PoweShell TTUC (Tips, Tricks and Useful Commands) #114 – Move Files and Folders

PowerShell TTUC (Tips, Tricks and Useful Commands) - #114

Create a folder and assign appreciate permission using PowerShell

$OutputLocation = "C:\Temp\Folder1"
$adminUser = "Domain\Admin1"

#
if (-not(test-path $OutputLocaiton))  #verify the existance of "C:\Temp\Folder1" fodler
{
    #if not create a new folder
    New-Item -ItemType directory -Path $OutputLocaiton | out-null
    $cACL = Get-Acl $OutputLocaiton
    $nACL = New-Object  system.security.accesscontrol.filesystemaccessrule($adminUser,"Fullcontrol","Allow")
    $cACL.SetAccessRule($nACL)
    Set-Acl $OutputLocaiton $cACL

}

Reference -  How to Handle NTFS Folder Permissions, Security Descriptors and ACLs in PowerShell

Read More

Update Group Membership – PowerShell Script

If you have multiple domains or performing a user or group migration, you may need to manually update (depend on your scenario) the source or target group membership.  This script can be used to update group membership based on source user’s group membership.  The input for this script the user name (sAMAccountName) and it assumes that the source and target sAMAccountName are the same. 

Input file (Users.csv) Format:

Script validates users in the source domain and collect “memberof” details and then add the target user (migrated user) to the same group. At the end of the operation, the source user and the target user (migrated user) will be part of same security group in the source domain. 

You can see some other “Update Group Membership” script here - http://portal.sivarajan.com/2014/01/update-group-membershippowershell-script.html

Script:

#

# Update Group Membership

# Santhosh Sivarajan (Santhosh@Sivarajan.Com)

#

Clear

Import-Module ActiveDirectory

$userN = ""

$GroupDetails = ""

$Group = ""

$GroupsDN = ""

$uValidation = ""

$tagetDomain = "labanddemo.com"

$Cdate = (Get-Date).tostring("dd-MM-yyyy-hh-mm-ss")

        $SGBeforeUpdateFile = New-Item -type file -force "C:\Temp\Groups_Before_$Cdate.csv"

        $SGAfterUpdateFile = New-Item -type file -force "C:\Temp\Groups_After_$Cdate.csv"

        Import-CSV "C:\Temp\Users.csv" | % {

        $userN = $_.userName

        $sourceDomain = $_.Domain

               

                   $uValidation = Get-ADUser -filter {sAMAccountName -eq $userN} -Server $tagetDomain

                  

                       If($uValidation -eq $Null)

                        {

                           Write-Host "User $userN Doesn't Exist in $tagetDomain Domain"

                           $errorFile = New-Item -type file -force "C:\Temp\Error_$Cdate.csv"

                           "User $userN Doesn't Exist in $tagetDomain Domain"| Out-File $errorFile -encoding ASCII -append

                        }

                        Else

                        {

                           $userN | Out-File $SGBeforeUpdateFile -encoding ASCII -append

                           $GroupDetails = get-aduser -Server $sourceDomain -identity $userN -Properties memberof

                           $GroupsDN = $GroupDetails.memberof

                           $GroupsDN | Out-File $SGBeforeUpdateFile -encoding ASCII -append

                           foreach ($Group in $GroupsDN)

                              {

                               $MigrateduserN = Get-ADUser $userN -Server $tagetDomain -Properties DistinguishedName

                               Write-host "Adding User -> $MigrateduserN"

                               Write-host "To Group -> $Group"

                               Add-ADGroupmember -Server $sourceDomain -Identity $Group -Members $MigrateduserN

                               $members = Get-ADGroupmember -Server $sourceDomain -Identity $Group

                               $GroupName = Get-ADGroup -Server $sourceDomain $Group

                               $GroupName.Name | Out-File $SGAfterUpdateFile -encoding ASCII -append

                               $members.distinguishedName | Out-File $SGAfterUpdateFile -encoding ASCII -append

                               Write-host "....Done!" -ForegroundColor Green

                               Write-host ""

                               }

                        }

        }

Download:

You can also download the script from the following locations:

1. OneDrive
2. TechNet Gallery 

Read More

Group Membership Report – PowerShell Script

Another “Group Membership Report” script.  You can see some of the previous versions here - http://portal.sivarajan.com/2010/08/list-group-members-in-active.html.

This script provides the group membership details based on user name.  You can include all user names in an input file (Users.csv) in the following format:

Script uses Get-ADUser cmdlet to validate the user first then get the user membership using the “memberof” properties.  Output/report will be in the GMReport_$Cdate.csv file.  Error message will be captured in Error_$Cdate.csv file.

Script:

#

#Group Membership Report – PowerShell Script

#Santhosh Sivarajan (santhosh@sivarajan.com)

#

Clear

Import-Module ActiveDirectory

$userN = ""

$GroupDetails = ""

$Group = ""

$GroupsDN = ""

$uValidation = ""

$Cdate = (Get-Date).tostring("dd-MM-yyyy-hh-mm-ss")

    $Report = New-Item -type file -force "C:\Temp\GMReport_$Cdate.csv"

    Import-CSV "C:\Temp\Users.csv" | % {

    $userN = $_.userName

    $sourceDomain = $_.Domain

    $uValidation = Get-ADUser -filter {sAMAccountName -eq $userN} -Server $sourceDomain

   

        If($uValidation -eq $Null)

             {

              Write-Host "User $userN Doesn't Exist in $sourceDomain Domain"

              $errorFile = New-Item -type file -force "C:\Temp\Error_$Cdate.csv"

              "User $userN Doesn't Exist in $sourceDomain Domain"| Out-File $errorFile -encoding ASCII -append

             }

         Else

             {

               

                $userN | Out-File $SGBeforeUpdateFile -encoding ASCII -append

                $GroupDetails = get-aduser -Server $sourceDomain -identity $userN -Properties memberof

                $GroupsDN = $GroupDetails.memberof

                $GroupsDN | Out-File $SGBeforeUpdateFile -encoding ASCII -append

            }

    }

Download:

You can also download the script from the following locations:

1. OneDrive
2. TechNet Gallery 

Read More

Advanced Threat Analytics–Attack Simulation and Demo – Part1

Advanced Threat Analytics–Attack Simulation and Demo–Part1

Advanced Threat Analytics–Attack Simulation and Demo–Part2

Advanced Threat Analytics–Attack Simulation and Demo–Part3

Microsoft Advanced Threat Analytics (ATA) is an user and entity behavior analytics solution to identify and protect protect organizations from advanced targeted attacks (APTs).  You can read more information about Microsoft Advanced Threat Analytics (ATA) here.  The purpose of this blog is to provide a few methods which can be used to simulate and demonstrate some of the basic attacks for demo and testing purpose.

Suspicious Activity Simulation #1 – ATA Gateway Stopped Communicating 

We will start with the most obvious one! – ATA communication issue.   In this scenario, I am using ATA Light Weight Gateway(LWGW).  In this case Microsoft Advanced Threat Analytics Gateway (ATAGateway) service should be running on Domain Controllers. 

To simulate this scenario,

1. Identify all Domain Controllers from the forest/domain. You can use the following DSQUERY command to get all DCs from the domain.  
   • DsQuery Server -Forest
2. Stop the ATAGateway service remotely
   • Here are a few scripts -  Script1 or Script2 or Script3 – if you want to go a script based approach
   • Or we can use a simple SC command – SC \\Lab-DC01 stop ATAGateway
   • 

You will receive the following high alert – ATA Gateway Stopped Communicating – in Health Center. 

Suspicious Activity Simulation #2- Honey Token Account Activities

In general, the Honey Token accounts are non-interactive accounts.  These accounts can be dummy accounts for detect malicious activities.

To simulate this scenario,

1. Create two 2 user accounts in Active Directory (ATA-Test1 and ATA-Test2)
2. Add ATA-Test2 to Domain Admins group
3. Get the SID of ATA-Test1 and ATA-Test2 using PowerShell or DSQUERY command
   • dsquery * -filter (samaccountname=ata-test1) -attr objectsid (Reference)
   • Get-ADUser Ata-test1 -Properties objectSID (Reference)
4. Add this SID as Honey token accounts (ATA Console –> Configuration –> Detection –> Honeytoken Account SIDs). Save the configuration. 
5. 
6. Establish an integrative logon session using these accounts. You can RDP into a machine use these accounts

Honey Token accounts (non-sensitive)

You will receive the following alert/email with recommended actions in the ATA console. 

Honey Token accounts (Sensitive)

Since ATA-Test2 account is a domain admin account, you will receive the same alert with "Sensitive (S )" indicating that this account is a high privileged account in Active Directory. 

Suspicious Activity Simulation #3 – Massive Object Deletion

Bulk object deletion can be a suspicious activity in an Active Directory environment.  ATA can alert alert you based on massive object deletion activities. 

To simulate this scenario,

1. Create a few users in Active directory. Here is a sample PowerShell  script which you can use to create test accounts in Active Directory

Clear
Import-module activedirectory
$pass = ConvertTo-SecureString "MyPassword0!" –asplaintext –force
for ($i=0;$i -lt 100;$i++)
{
$accountname = "Test-Account$i"
Write-Host "Creating $accountname" -NoNewline
New-ADUser –SamAccountName $accountname –name $accountname -OtherAttributes @{'description'="ATA Test User Account"} -Path "OU=Test Accounts,OU=User Accounts,DC=labanddemo,DC=com"
Set-ADAccountPassword –identity $accountname –NewPassword $pass
Write-Host "...Done"
}

1. Make sure ATA is "learned" about these account.
2. 
3. Delete these accounts from Active Directory 

You will receive the Massive Object Deletion alert in the ATA console right away as shown below. 

Suspicious Activity Simulation #4 - Reconnaissance using DNS

The DNS or name resolution information in a network would be  useful reconnaissance information. In general, DNS data contains a list of all the servers and workstations and the mapping to their IP addresses. Verifying this  information may provide attackers with a detailed view of the environment allowing attackers to focus their efforts on the relevant entities. 

For this simulation, the plan is to perform a DNS zone lookup using NSLOOKUP LS command. 

To simulate this scenario,

1. Logon to a remote server. 
2. Open Command Prompt and run NSLOOKUP command
3. From the NSLOOKUP window, run LS command to list the DNS zone

You will receive the following Reconnaissance using DNS alert the ATA console. 

Advanced Threat Analytics–Attack Simulation and Demo–Part1

Advanced Threat Analytics–Attack Simulation and Demo–Part2

Advanced Threat Analytics–Attack Simulation and Demo–Part3

Read More

Configuring Deepnet Security SafeID OATH Token with Microsoft Azure MFA Server

Related Blogs:

Configuring YubiKey / Yubico OATH Token with Microsoft Azure MFA Server - http://portal.sivarajan.com/2016/06/configuring-yubikey-yubico-oath-token.html
Azure MFA with pGina and Local Authentication - http://portal.sivarajan.com/2015/09/azure-mfa-with-pgina.html

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

Microsoft Azure MFA on-premises server supports a time based OATH (OATH – TOTP) third party tokens.  This is an alternative to using the Azure Authenticator Mobile App as an OATH token.  You can see other MFA authentication options in my Azure MFA Server–Authentication Types (Part I) and Azure MFA Server–Authentication Types (Part II) blogs.  The OATH tokens can be added or imported prior to being associated with a user.  Administrators can associate users and tokens in the Multi-Factor Authentication Server  or the User Portal.  Users can associate themselves with an OATH token during User Portal enrollment or using the OATH Token menu option when the User Portal is configured to provide this functionality.    A bulk token import and configuration is also supported by MFA Server .  An administrator can import OATH Token records from an input  file .  The secret keys must be in Base32 format. 

This blog provides step-by-step instructions in configuring Deepnet SafeID OATH token with Microsoft Azure MFA server.  I am using DeepNet Security's SafeID Classic model for this testing.  You can review different token models and details on their website.  

Requirements:

The following are the pre-requirements to complete this configuration. 

1. Microsoft Azure MFA on-premises server
2. Deepnet SafeID hardware
3. Secret Key for your DeepNet SafeID.  You will receive an email with Secret Key after the purchase. 

Review the following Azure MFA Server Authentication Types  blog if you are not familiar with authentication configuration in Azure MFA Server:

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

Azure MFA Server – Configuration for third Party OATH

First step in this process is to add third party OATH Tokens in Azure MFA Server. You can either add these tokens individually or perform a bulk import using an input file. 

To add an OATH token,

1. Logon to your MFA application server.  Open Multi-Factor Authentication Server UI and Select OATH Token icon.
2. Click Add option from OATH Token window.
3. 
4. Enter your Secret Key token Details
   1. Serial Number – Required.  Enter the  serial number of your SafeID. This will be in the back of the Secret Keyas shown below or it will be the email you received from DeepNet. 
   2. 
   3. Secret Key – Required. This is the Secret Key (Base32).  You have to receive this information from DeepNet.    You will receive an email from Deepnet with Secret Key after the purchase
   4. Manufacturer – Optional.  Enter DeepNet Security as the manufacturer.
   5. Model – Optional.  Enter SafeID as model type. 
   6. Start date – Optional
   7. Expiration date – Optional
   8. Time interval – Required. Select 60 seconds. 
   9. Username:  Associate a user with this OATH token.  You can manually enter the username or Select Useroption to identify a user. 
   10. 
   11. Click OK to complete.  The Synchronize OATH Token dialog will prompt for the current OATH code to synchronize the OATH token and verify the configuration.
   12. 
   13. Enter the current code from DeepNet SafeID from the Synchronize OATH Token window to complete token configuration in MFA Server.  Click OK. 
   14. 

Note1: MFA server validates the OATH code against the OATH token secret key and synchronizes the OATH token's time if they are valid.  If there are not valid, you will see the following error message:

Note2: Azure Multi-Factor Authentication Server supports bulk import of token records by using an input CSV file.   The file must be in a supported format and may be partially or fully encrypted with a password. 

Sample Input File

To perform a bulk import,

Note3: you may receive the following error message when you click on Import button. There is an update/hotfix for this issue. 

Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately. 

Could not load file or assembly ‘PfPskcClr, Version=0.0.0.0, Culture=neutral, PublicKey Token=null’ or one of its dependencies.  A strongly-named assembly is required.  (Exception from HRRESULT:0X8013100) 

Azure MFA Server – End User Validation Using DeepNet SafeID OATH Token

The final step in this process is to validate the DeepNet SafeID configuration and authentication experience from an end user perspective. 

To configure OATH token as the authentication type for an end user:

1. From Multi-Factor Authentication Server UI, Select Users icon
2. From right pane, open the user properties by double clicking the user object.
3. This will open User Properties / Edit User  window as shown below.  Make sure that the OATH Token is selected as the authentication type for this test user. 
5. 
6. To validate this configuration, select out test user object and from the bottom of the window, select Test option.  
7. 
8. User will be prompted for first /primary authentication using a user name and password. Enter the User name and Password for the user, then click Test. 
9. 
10. Then it will prompt you for the secondary authentication.  In this scenario, it the OATH Code.
11. Get the current OATH code from your DeepNet SafeID. 
12. 
13. Enter the current code in the OATH Code window in the MFA application .  Click OK. 
14. 
15. You will see the authentication status/result as shown below: 
16. 

Related Blogs:

Configuring YubiKey / Yubico OATH Token with Microsoft Azure MFA Server - http://portal.sivarajan.com/2016/06/configuring-yubikey-yubico-oath-token.html
Azure MFA with pGina and Local Authentication - http://portal.sivarajan.com/2015/09/azure-mfa-with-pgina.html

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

Read More

Configuring YubiKey / Yubico OATH Token with Microsoft Azure MFA Server

Related blogs:

Configuring Deepnet Security SafeID OATH Token with Microsoft Azure MFA Server  - http://portal.sivarajan.com/2016/07/configuring-deepnet-security-safeid.html
Azure MFA with pGina and Local Authentication - http://portal.sivarajan.com/2015/09/azure-mfa-with-pgina.html

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

Microsoft Azure MFA on-premises server supports a time based OATH (OATH – TOTP) third party tokens.  This is an alternative to using the Azure Authenticator Mobile App as an OATH token.  You can see other MFA authentication options in my Azure MFA Server–Authentication Types (Part I) and Azure MFA Server–Authentication Types (Part II) blogs.  The OATH tokens can be added or imported prior to being associated with a user.  Administrators can associate users and tokens in the Multi-Factor Authentication Server  or the User Portal.  Users can associate themselves with an OATH token during User Portal enrollment or using the OATH Token menu option when the User Portal is configured to provide this functionality.    A bulk token import and configuration is also supported by MFA Server .  An administrator can import OATH Token records from an input  file .  The secret keys must be in Base32 format.  This blog provides step-by-step instructions in configuring YubiKey OATH token with Microsoft Azure MFA server. 

Requirements:

The following are the pre-requirements to complete this configuration. 

1. Microsoft Azure MFA on-premises server
2. YubiKey hardware
3. YubiKey Personalization Tool
4. YubiCo Authenticator Application

YubiKey Personalization Tool – Installation and Configuration

Microsoft Azure MFA server supports only the OATH TOTP (time-based) tokens.  So you need to make sure that your YubiKey is in Yubico OTP Mode using the YubiKey Personalization Tool. Other configurations are optional for Microsoft Azure MFA server configuration and testing. 

The YubiKey Personalization Tool can be used to program the two configuration slots. Also, it can be used to personalize the YubiKey in the following modes:

• Yubico OTP
• OATH-HOTP
• Static Password
• Challenge-Response

Download YubiKey Personalization Tool and run yubikey-personalization-gui-3.1.24.exe  file to compete the tool installation. 

1. Insert YubiKey into the USB port.  You may see the Device Setup windows as shown below.  Complete the drive installation process.  
2. Open YubiKey Personalization Tool. Make sure:
   1. YubiKey Personalization Tool has successfully identified your YubiKey. 
   2. 
   3. Yubico OTP displayed as supported method in Features Supported section. 
   4. 
3. You will see all the current OTP configuration in Yubico OTP tab shown below. I am going to a use the default configuration for this testing. 
4. 

YubiCo Authenticator Application – Installation and Configuration

Download YubiCo Authenticator Application and run yubioath-desktop-3.0.1-win.exe file to complete the application installation. 

1. Open YubiCo Authenticator Application
2. From File menu, select Add option (File –> Add)
3. 
4. From the New Credential window:
   1. Enter Credential Name – An identifier or a display name for the credential.
   2. Secret Key – It is a Base32 key. Review this If you are not familiar with supported numbers or characters in Base32 encoding. 
   3. Select Time based (TOTP) option.  Microsoft Azure MFA server supports only the OATH TOTP (time-based)tokens. 
   4. Number of digits – You can select 6 or 8 digits as OATH token length.
   5. 
   6. Require touch -  If you select this option, end user has to touch the YubiKey to generate an OATH token.  User will prompted with the following message:
   7. 
   8. Click OK to save the configuration
   9. 
   10. You will see the newly add account in the Yubico Authenticator window. 
   11. 

Now we have completed the YubiKey account configuration. We can move on to Azure MFA server to configure the OATH token.

Azure MFA Server - Configuration for third Party OATH

Review the following Azure MFA Server Authentication Types  blog if you are not familiar with authentication configuration in Azure MFA Server:

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

To add OATH Token in Azure MFA Server,

1. Open Multi-Factor Authentication Server UI and Select OATH Token icon.
2. Click Add option from OATH Token window.
3. 
4. Enter your YubiKey token Details
   1. Serial Number – Required.  Enter the YubiKey serial number. This will be in the back of the Yubikey as shown below:
   2. 
   3. Secret Key – Required. This is the Secret Key (Base32) you have configured using the Authentication Application. 
   4. Manufacturer – Optional.  Enter Youbico as the manufacturer.
   5. Model – Optional.  Enter your YubiKey model type. 
   6. Start date – Optional
   7. Expiration date – Optional
   8. Time interval – Required. You can select the default 30 seconds value.  By default, YubiKey changes the 6-8 digit code  every 30 seconds. 
   9. Username:  Select the user for this OATH token.  You manually enter the username or Select User option to identify a user. 
   10. Click OK to complete.  The Synchronize OATH Token dialog will prompt for the current OATH code to synchronize the OATH token and verify the configuration.
   11. 
   12. Generate a new OATH from Yubico Authentication app using the button. 
   13. 
   14. Enter this code in the Synchronize OATH Token window to complete token configuration in MFA Server. 

Note1: MFA server validates the OATH code against the OATH token secret key and synchronizes the OATH token's time if they are valid.  If there are not valid, you will see the following error message:

Note2: Azure Multi-Factor Authentication Server supports bulk import of token records by using an input CSV file.   The file must be in a supported format and may be partially or fully encrypted with a password. 

Sample Input File

To perform a bulk import,

1. Select OATH Token icon and select Import.
2. Select the input file and click Import.

Note3: you may receive the following error message when you click on Import button. There is an update/hotfix for this issue. 

Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately. 

Could not load file or assembly ‘PfPskcClr, Version=0.0.0.0, Culture=neutral, PublicKey Token=null’ or one of its dependencies.  A strongly-named assembly is required.  (Exception from HRRESULT:0X8013100) 

Azure MFA Server – End User Validation Using YubiKey OATH Token

The final step in this process is to validate the YubiKey configuration and authentication experience from an end user perspective. 

To configure OATH token as the authentication type for an end user:

1. From Multi-Factor Authentication Server UI, Select Users icon
2. From right pane, open the user properties by double clicking the user object.
3. This will open User Properties / Edit User  window as shown below.  Make sure that the OATH Token is selected as the authentication type for this test user. 
5. 
6. To validate this configuration, select out test user object and from the bottom of the window, select Test option.  
7. 
8. User will be prompted for first /primary authentication using a user name and password. Enter the User name and Password for the user, then click Test. 
9. 
10. Then it will prompt you for the secondary authentication.  In this scenario, it the OATH Code.
11. To generate a new OATH code, open Yubico Authenticator App and  pressing the button .  The OATH code will be displayed as shown below:
12. 
13. Enter the current OATH code in the OATH Code in the MFA application window.  Click OK.  
14. You will see the authentication status/result as shown below: 
15. 

Related blogs:

Configuring Deepnet Security SafeID OATH Token with Microsoft Azure MFA Server  - http://portal.sivarajan.com/2016/07/configuring-deepnet-security-safeid.html
Azure MFA with pGina and Local Authentication - http://portal.sivarajan.com/2015/09/azure-mfa-with-pgina.html

Azure MFA Server –Authentication Types (Part I) - http://portal.sivarajan.com/2016/05/azure-mfa-serverauthentication-type.html
Azure MFA Server –Authentication Types (Part II) - http://portal.sivarajan.com/2016/06/azure-mfa-server-authentication-type.html

Read More