How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

This key's fingerprint is A04C 5E09 ED02 B328 03EB 6116 93ED 732E 9231 8DBA

    -----BEGIN PGP PUBLIC KEY BLOCK-----

    mQQNBFUoCGgBIADFLp+QonWyK8L6SPsNrnhwgfCxCk6OUHRIHReAsgAUXegpfg0b
    rsoHbeI5W9s5to/MUGwULHj59M6AvT+DS5rmrThgrND8Dt0dO+XW88bmTXHsFg9K
    jgf1wUpTLq73iWnSBo1m1Z14BmvkROG6M7+vQneCXBFOyFZxWdUSQ15vdzjr4yPR
    oMZjxCIFxe+QL+pNpkXd/St2b6UxiKB9HT9CXaezXrjbRgIzCeV6a5TFfcnhncpO
    ve59rGK3/az7cmjd6cOFo1Iw0J63TGBxDmDTZ0H3ecQvwDnzQSbgepiqbx4VoNmH
    OxpInVNv3AAluIJqN7RbPeWrkohh3EQ1j+lnYGMhBktX0gAyyYSrkAEKmaP6Kk4j
    /ZNkniw5iqMBY+v/yKW4LCmtLfe32kYs5OdreUpSv5zWvgL9sZ+4962YNKtnaBK3
    1hztlJ+xwhqalOCeUYgc0Clbkw+sgqFVnmw5lP4/fQNGxqCO7Tdy6pswmBZlOkmH
    XXfti6hasVCjT1MhemI7KwOmz/KzZqRlzgg5ibCzftt2GBcV3a1+i357YB5/3wXE
    j0vkd+SzFioqdq5Ppr+//IK3WX0jzWS3N5Lxw31q8fqfWZyKJPFbAvHlJ5ez7wKA
    1iS9krDfnysv0BUHf8elizydmsrPWN944Flw1tOFjW46j4uAxSbRBp284wiFmV8N
    TeQjBI8Ku8NtRDleriV3djATCg2SSNsDhNxSlOnPTM5U1bmh+Ehk8eHE3hgn9lRp
    2kkpwafD9pXaqNWJMpD4Amk60L3N+yUrbFWERwncrk3DpGmdzge/tl/UBldPoOeK
    p3shjXMdpSIqlwlB47Xdml3Cd8HkUz8r05xqJ4DutzT00ouP49W4jqjWU9bTuM48
    LRhrOpjvp5uPu0aIyt4BZgpce5QGLwXONTRX+bsTyEFEN3EO6XLeLFJb2jhddj7O
    DmluDPN9aj639E4vjGZ90Vpz4HpN7JULSzsnk+ZkEf2XnliRody3SwqyREjrEBui
    9ktbd0hAeahKuwia0zHyo5+1BjXt3UHiM5fQN93GB0hkXaKUarZ99d7XciTzFtye
    /MWToGTYJq9bM/qWAGO1RmYgNr+gSF/fQBzHeSbRN5tbJKz6oG4NuGCRJGB2aeXW
    TIp/VdouS5I9jFLapzaQUvtdmpaeslIos7gY6TZxWO06Q7AaINgr+SBUvvrff/Nl
    l2PRPYYye35MDs0b+mI5IXpjUuBC+s59gI6YlPqOHXkKFNbI3VxuYB0VJJIrGqIu
    Fv2CXwy5HvR3eIOZ2jLAfsHmTEJhriPJ1sUG0qlfNOQGMIGw9jSiy/iQde1u3ZoF
    so7sXlmBLck9zRMEWRJoI/mgCDEpWqLX7hTTABEBAAG0x1dpa2lMZWFrcyBFZGl0
    b3JpYWwgT2ZmaWNlIEhpZ2ggU2VjdXJpdHkgQ29tbXVuaWNhdGlvbiBLZXkgKFlv
    dSBjYW4gY29udGFjdCBXaWtpTGVha3MgYXQgaHR0cDovL3dsY2hhdGMzcGp3cGxp
    NXIub25pb24gYW5kIGh0dHBzOi8vd2lraWxlYWtzLm9yZy90YWxrKSA8Y29udGFj
    dC11cy11c2luZy1vdXItY2hhdC1zeXN0ZW1Ad2lraWxlYWtzLm9yZz6JBD0EEwEK
    ACcCGwMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AFAlb6cdIFCQOznOoACgkQk+1z
    LpIxjbrlqh/7B2yBrryWhQMGFj+xr9TIj32vgUIMohq94XYqAjOnYdEGhb5u5B5p
    BNowcqdFB1SOEvX7MhxGAqYocMT7zz2AkG3kpf9f7gOAG7qA1sRiB+R7mZtUr9Kv
    fQSsRFPb6RNzqqB9I9wPNGhBh1YWusUPluLINwbjTMnHXeL96HgdLT+fIBa8ROmn
    0fjJVoWYHG8QtsKiZ+lo2m/J4HyuJanAYPgL6isSu/1bBSwhEIehlQIfXZuS3j35
    12SsO1Zj2BBdgUIrADdMAMLneTs7oc1/PwxWYQ4OTdkay2deg1g/N6YqM2N7rn1W
    7A6tmuH7dfMlhcqw8bf5veyag3RpKHGcm7utDB6k/bMBDMnKazUnM2VQoi1mutHj
    kTCWn/vF1RVz3XbcPH94gbKxcuBi8cjXmSWNZxEBsbirj/CNmsM32Ikm+WIhBvi3
    1mWvcArC3JSUon8RRXype4ESpwEQZd6zsrbhgH4UqF56pcFT2ubnqKu4wtgOECsw
    K0dHyNEiOM1lL919wWDXH9tuQXWTzGsUznktw0cJbBVY1dGxVtGZJDPqEGatvmiR
    o+UmLKWyxTScBm5o3zRm3iyU10d4gka0dxsSQMl1BRD3G6b+NvnBEsV/+KCjxqLU
    vhDNup1AsJ1OhyqPydj5uyiWZCxlXWQPk4p5WWrGZdBDduxiZ2FTj17hu8S4a5A4
    lpTSoZ/nVjUUl7EfvhQCd5G0hneryhwqclVfAhg0xqUUi2nHWg19npPkwZM7Me/3
    +ey7svRUqxVTKbXffSOkJTMLUWqZWc087hL98X5rfi1E6CpBO0zmHeJgZva+PEQ/
    ZKKi8oTzHZ8NNlf1qOfGAPitaEn/HpKGBsDBtE2te8PF1v8LBCea/d5+Umh0GELh
    5eTq4j3eJPQrTN1znyzpBYkR19/D/Jr5j4Vuow5wEE28JJX1TPi6VBMevx1oHBuG
    qsvHNuaDdZ4F6IJTm1ZYBVWQhLbcTginCtv1sadct4Hmx6hklAwQN6VVa7GLOvnY
    RYfPR2QA3fGJSUOg8xq9HqVDvmQtmP02p2XklGOyvvfQxCKhLqKi0hV9xYUyu5dk
    2L/A8gzA0+GIN+IYPMsf3G7aDu0qgGpi5Cy9xYdJWWW0DA5JRJc4/FBSN7xBNsW4
    eOMxl8PITUs9GhOcc68Pvwyv4vvTZObpUjZANLquk7t8joky4Tyog29KYSdhQhne
    oVODrdhTqTPn7rjvnwGyjLInV2g3pKw/Vsrd6xKogmE8XOeR8Oqk6nun+Y588Nsj
    XddctWndZ32dvkjrouUAC9z2t6VE36LSyYJUZcC2nTg6Uir+KUTs/9RHfrvFsdI7
    iMucdGjHYlKc4+YwTdMivI1NPUKo/5lnCbkEDQRVKAhoASAAvnuOR+xLqgQ6KSOO
    RTkhMTYCiHbEsPmrTfNA9VIip+3OIzByNYtfFvOWY2zBh3H2pgf+2CCrWw3WqeaY
    wAp9zQb//rEmhwJwtkW/KXDQr1k95D5gzPeCK9R0yMPfjDI5nLeSvj00nFF+gjPo
    Y9Qb10jp/Llqy1z35Ub9ZXuA8ML9nidkE26KjG8FvWIzW8zTTYA5Ezc7U+8HqGZH
    VsK5KjIO2GOnJiMIly9MdhawS2IXhHTV54FhvZPKdyZUQTxkwH2/8QbBIBv0OnFY
    3w75Pamy52nAzI7uOPOU12QIwVj4raLC+DIOhy7bYf9pEJfRtKoor0RyLnYZTT3N
    0H4AT2YeTra17uxeTnI02lS2Jeg0mtY45jRCU7MrZsrpcbQ464I+F411+AxI3NG3
    cFNJOJO2HUMTa+2PLWa3cERYM6ByP60362co7cpZoCHyhSvGppZyH0qeX+BU1oyn
    5XhT+m7hA4zupWAdeKbOaLPdzMu2Jp1/QVao5GQ8kdSt0n5fqrRopO1WJ/S1eoz+
    Ydy3dCEYK+2zKsZ3XeSC7MMpGrzanh4pk1DLr/NMsM5L5eeVsAIBlaJGs75Mp+kr
    ClQL/oxiD4XhmJ7MlZ9+5d/o8maV2K2pelDcfcW58tHm3rHwhmNDxh+0t5++i30y
    BIa3gYHtZrVZ3yFstp2Ao8FtXe/1ALvwE4BRalkh+ZavIFcqRpiF+YvNZ0JJF52V
    rwL1gsSGPsUY6vsVzhpEnoA+cJGzxlor5uQQmEoZmfxgoXKfRC69si0ReoFtfWYK
    8Wu9sVQZW1dU6PgBB30X/b0Sw8hEzS0cpymyBXy8g+itdi0NicEeWHFKEsXa+HT7
    mjQrMS7c84Hzx7ZOH6TpX2hkdl8Nc4vrjF4iff1+sUXj8xDqedrg29TseHCtnCVF
    kfRBvdH2CKAkbgi9Xiv4RqAP9vjOtdYnj7CIG9uccek/iu/bCt1y/MyoMU3tqmSJ
    c8QeA1L+HENQ/HsiErFGug+Q4Q1SuakHSHqBLS4TKuC+KO7tSwXwHFlFp47GicHe
    rnM4v4rdgKic0Z6lR3QpwoT9KwzOoyzyNlnM9wwnalCLwPcGKpjVPFg1t6F+eQUw
    WVewkizhF1sZBbED5O/+tgwPaD26KCNuofdVM+oIzVPOqQXWbaCXisNYXoktH3Tb
    0X/DjsIeN4TVruxKGy5QXrvo969AQNx8Yb82BWvSYhJaXX4bhbK0pBIT9fq08d5R
    IiaN7/nFU3vavXa+ouesiD0cnXSFVIRiPETCKl45VM+f3rRHtNmfdWVodyXJ1O6T
    ZjQTB9ILcfcb6XkvH+liuUIppINu5P6i2CqzRLAvbHGunjvKLGLfvIlvMH1mDqxp
    VGvNPwARAQABiQQlBBgBCgAPAhsMBQJW+nHeBQkDs5z2AAoJEJPtcy6SMY26Qtgf
    /0tXRbwVOBzZ4fI5NKSW6k5A6cXzbB3JUxTHMDIZ93CbY8GvRqiYpzhaJVjNt2+9
    zFHBHSfdbZBRKX8N9h1+ihxByvHncrTwiQ9zFi0FsrJYk9z/F+iwmqedyLyxhIEm
    SHtWiPg6AdUM5pLu8GR7tRHagz8eGiwVar8pZo82xhowIjpiQr0Bc2mIAusRs+9L
    jc+gjwjbhYIg2r2r9BUBGuERU1A0IB5Fx+IomRtcfVcL/JXSmXqXnO8+/aPwpBuk
    bw8sAivSbBlEu87P9OovsuEKxh/PJ65duQNjC+2YxlVcF03QFlFLGzZFN7Fcv5JW
    lYNeCOOz9NP9TTsR2EAZnacNk75/FYwJSJnSblCBre9xVA9pI5hxb4zu7CxRXuWc
    QJs8Qrvdo9k4Jilx5U9X0dsiNH2swsTM6T1gyVKKQhf5XVCS4bPWYagXcfD9/xZE
    eAhkFcAuJ9xz6XacT9j1pw50MEwZbwDneV93TqvHmgmSIFZow1aU5ACp+N/ksT6E
    1wrWsaIJjsOHK5RZj/8/2HiBftjXscmL3K8k6MbDI8P9zvcMJSXbPpcYrffw9A6t
    ka9skmLKKFCcsNJ0coLLB+mw9DVQGc2dPWPhPgtYZLwG5tInS2bkdv67qJ4lYsRM
    jRCW5xzlUZYk6SWD4KKbBQoHbNO0Au8Pe/N1SpYYtpdhFht9fGmtEHNOGPXYgNLq
    VTLgRFk44Dr4hJj5I1+d0BLjVkf6U8b2bN5PcOnVH4Mb+xaGQjqqufAMD/IFO4Ro
    TjwKiw49pJYUiZbw9UGaV3wmg+fue9To1VKxGJuLIGhRXhw6ujGnk/CktIkidRd3
    5pAoY5L4ISnZD8Z0mnGlWOgLmQ3IgNjAyUzVJRhDB5rVQeC6qX4r4E1xjYMJSxdz
    Aqrk25Y//eAkdkeiTWqbXDMkdQtig2rY+v8GGeV0v09NKiT+6extebxTaWH4hAgU
    FR6yq6FHs8mSEKC6Cw6lqKxOn6pwqVuXmR4wzpqCoaajQVz1hOgD+8QuuKVCcTb1
    4IXXpeQBc3EHfXJx2BWbUpyCgBOMtvtjDhLtv5p+4XN55GqY+ocYgAhNMSK34AYD
    AhqQTpgHAX0nZ2SpxfLr/LDN24kXCmnFipqgtE6tstKNiKwAZdQBzJJlyYVpSk93
    6HrYTZiBDJk4jDBh6jAx+IZCiv0rLXBM6QxQWBzbc2AxDDBqNbea2toBSww8HvHf
    hQV/G86Zis/rDOSqLT7e794ezD9RYPv55525zeCk3IKauaW5+WqbKlwosAPIMW2S
    kFODIRd5oMI51eof+ElmB5V5T9lw0CHdltSM/hmYmp/5YotSyHUmk91GDFgkOFUc
    J3x7gtxUMkTadELqwY6hrU8=
    =BLTH
    -----END PGP PUBLIC KEY BLOCK-----

How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

### Contact

If you need help using Tor you can contact WikiLeaks for assistance in setting it up using our simple webchat available at: https://wikileaks.org/talk

If you can use Tor, but need to contact WikiLeaks for other reasons use our secured webchat available at http://wlchatc3pjwpli5r.onion

We recommend contacting us over Tor if you can.

How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

### Tor

Tor is an encrypted anonymising network that makes it harder to intercept internet communications, or see where communications are coming from or going to.

In order to use the WikiLeaks public submission system as detailed above you can download the Tor Browser Bundle, which is a Firefox-like browser available for Windows, Mac OS X and GNU/Linux and pre-configured to connect using the anonymising system Tor.

#### Tails

If you are at high risk and you have the capacity to do so, you can also access the submission system through a secure operating system called Tails. Tails is an operating system launched from a USB stick or a DVD that aim to leaves no traces when the computer is shut down after use and automatically routes your internet traffic through Tor. Tails will require you to have either a USB stick or a DVD at least 4GB big and a laptop or desktop computer.

How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

### Tips

Our submission system works hard to preserve your anonymity, but we recommend you also take some of your own precautions. Please review these basic guidelines.

#### 1. Contact us if you have specific problems

If you have a very large submission, or a submission with a complex format, or are a high-risk source, please contact us. In our experience it is always possible to find a custom solution for even the most seemingly difficult situations.

#### 2. What computer to use

If the computer you are uploading from could subsequently be audited in an investigation, consider using a computer that is not easily tied to you. Technical users can also use Tails to help ensure you do not leave any records of your submission on the computer.

#### 3. Do not talk about your submission to others

If you have any issues talk to WikiLeaks. We are the global experts in source protection – it is a complex field. Even those who mean well often do not have the experience or expertise to advise properly. This includes other media organisations.

How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

### After

#### 1. Do not talk about your submission to others

If you have any issues talk to WikiLeaks. We are the global experts in source protection – it is a complex field. Even those who mean well often do not have the experience or expertise to advise properly. This includes other media organisations.

#### 2. Act normal

If you are a high-risk source, avoid saying anything or doing anything after submitting which might promote suspicion. In particular, you should try to stick to your normal routine and behaviour.

#### 3. Remove traces of your submission

If you are a high-risk source and the computer you prepared your submission on, or uploaded it from, could subsequently be audited in an investigation, we recommend that you format and dispose of the computer hard drive and any other storage media you used.

In particular, hard drives retain data after formatting which may be visible to a digital forensics team and flash media (USB sticks, memory cards and SSD drives) retain data even after a secure erasure. If you used flash media to store sensitive data, it is important to destroy the media.

If you do this and are a high-risk source you should make sure there are no traces of the clean-up, since such traces themselves may draw suspicion.

#### 4. If you face legal action

If a legal action is brought against you as a result of your submission, there are organisations that may help you. The Courage Foundation is an international organisation dedicated to the protection of journalistic sources. You can find more details at https://www.couragefound.org.

# Submit documents to WikiLeaks

WikiLeaks publishes documents of political or historical importance that are censored or otherwise suppressed. We specialise in strategic global publishing and large archives.

The following is the address of our secure site where you can anonymously upload your documents to WikiLeaks editors. You can only access this submissions system through Tor. (See our Tor tab for more information.) We also advise you to read our tips for sources before submitting.

wlupld3ptjvsgwqw.onion
Copy this address into your Tor browser. Advanced users, if they wish, can also add a further layer of encryption to their submission using our public PGP key.

If you cannot use Tor, or your submission is very large, or you have specific requirements, WikiLeaks provides several alternative methods. Contact us to discuss how to proceed.

How to contact WikiLeaks? What is Tor? Tips for Sources After Submitting

# Vault7: CIA Hacking Tools Revealed

Navigation: » Directory » Network Devices Branch (NDB) » Network Devices Branch » Operations/Testing » JQJADVERSE

Owner: User #71467

## HG v3.1.3-Adverse-01 Testing

HG was delivered for JQJADVERSE on 9/8/15 for the Cisco 3560G. Testing scope will include testing ROCEM v1.2 for ADVERSE, delivered to Test Range on 9/15/15, as well as testing HG Base functionality, DNS Domain Name System Checkin capability, SDC Microsoft software packaging format comms, SMITE and on-device OPSEC since this will be a persistent delivery. Also need to test failsafe uninstall to ensure if comms are not established that HG bugs out.

CONOP will be

- Flux into network through three different hosts - first a webserver, then a DC, then to a host that is connected to an adjacent 2960 on a management subnet
- Trigger will be sent through flux, and CT Counter Terrorism session will be established back through flux initially
- An initial CT Counter Terrorism session will be established and DNS Domain Name System Checkin capability verified.
- Subsequent comms with HG will be via DNS Domain Name System checkin.
- DNS Checkin has been preconfigured with capability to execute SMITE

## Testing Summary

- Found issue that appears to match EAR Enterprise Archive 5012 - sent to Xetron to confirm this is the same issue.
- Observed EAR Enterprise Archive 5163 - Known issue
- Observed EAR Enterprise Archive 2036 - Known issue - Boot persistence not reported accurately in output of module show
- Validated EAR Enterprise Archive 5078 - Fixed
- Be aware that checkin variance should be changed before delay if you are updating both values
- How long before trigger seq / time to checkin are persisted? Question for Xetron
- HG-7 - HG does not squelch ICMP Internet Control Message Protocol unreachable response to DNSCheckin query
- HG-8 - HG does not set DF bit
- HG-9 - HG does not detect HTTPS Hypertext Transfer Protocol Secure clients to impersonate when https proxy uses port other than 443
- HG-10 - EAR Enterprise Archive 5536 - HG does not make CT Counter Terrorism session to external IP

## Testing Notes

Information about target:

- Hardware is WS-C3560G-24TS-S ( DUT is WS-C3560G-24PS-E)
- Software is c3560-ipbase-mz.122-35.SE5
- BOOTLDR: C3560 Boot Loader (C3560-HBOOT-M) Version 12.2(25r)SEE4, RELEASE SOFTWARE (fc1)

VMs Used

- Adverse-Flux1 - XX.XX.XXX.XX (IR-DATAK-20020718[IR])/192.168.0.21
- Adverse-Flux2/BIND - 192.168.0.11
- Adverse-Flux3 - 192.168.221.40
- Adverse-ICON-Debian8 - 172.20.12.34
- Adverse-Proxy - XX.XX.XXX.X (IR-DATAK-20020718[IR])/192.168.0.4
- Adverse-Seeds - 192.168.211.10
- DNS Server - X.X.X.X (LVLT-GOGL-8-8-8[US])
- DNS forwarding server 4.4.4.4

1. Smoke Test of ROCEM
   1. Set up the Flux nodes to hop through Flux1 -> Flux2 -> Flux3.
   2. Added a route on ICON VM Virtual Machine for 192.168.0.0/24 to point to the Flux tunnel.
   3. Started ROCEM interactive session - successful:

      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem# ./rocem_c3560-ipbase-mz.122-35.SE5.py -i 192.168.0.254
      [+] Validating data/interactive.bin
      [+] Validating data/set.bin
      [+] Validating data/transfer.bin
      [+] Validating data/unset.bin

      ****************************************
      Image: c3560-ipbase-mz.122-35.SE5
      Host: 192.168.0.254
      Action: Interactive
      ****************************************

      Proceed? (y/n)y
      Trying 127.0.0.1...
      [*] Attempting connection to host 192.168.0.254:23
      Connected to 127.0.0.1.
      Escape character is '^]'.
      [+] Connection established
      [*] Starting interactive session

      User Access Verification

      Password:
      MLS-Sth#

      MLS-Sth# show priv
      Current privilege level is 15
      MLS-Sth#show users
      Line User Host(s) Idle Location
      * 1 vty 0 idle 00:00:00 192.168.221.40

      Interface User Mode Idle Peer Address

      MLS-Sth#exit
      Connection closed by foreign host.
      [+] Unsetting
      [*] Attempting connection to host 192.168.0.254:23
      [+] Connection established
      [*] Sending Protocol Step 1
      [*] Sending Protocol Step 2
      [+] Done
      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem#

   4. Set/Unset ROCEM - Successful

   5. oot@ debian:/home/user1/ops/adverse/adverse-1r/rocem# ./rocem_c3560-ipbase-mz.122-35.SE5.py -s 192.168.0.254
      [+] Validating data/interactive.bin
      [+] Validating data/set.bin
      [+] Validating data/transfer.bin
      [+] Validating data/unset.bin

      ****************************************
      Image: c3560-ipbase-mz.122-35.SE5
      Host: 192.168.0.254
      Action: Set
      ****************************************

      Proceed? (y/n)y
      [*] Attempting connection to host 192.168.0.254:23
      [+] Connection established
      [*] Sending Protocol Step 1
      [*] Sending Protocol Step 2
      [+] Done
      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem# telnet 192.168.0.254
      Trying 192.168.0.254...
      Connected to 192.168.0.254.
      Escape character is '^]'.

      MLS-Sth#exit
      Connection closed by foreign host.
      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem# ./rocem_c3560-ipbase-mz.122-35.SE5.py -u 192.168.0.254
      [+] Validating data/interactive.bin
      [+] Validating data/set.bin
      [+] Validating data/transfer.bin
      [+] Validating data/unset.bin

      ****************************************
      Image: c3560-ipbase-mz.122-35.SE5
      Host: 192.168.0.254
      Action: Unset
      ****************************************

      Proceed? (y/n)y
      [*] Attempting connection to host 192.168.0.254:23
      [+] Connection established
      [*] Sending Protocol Step 1
      [*] Sending Protocol Step 2
      [+] Done
      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem# telnet 192.168.0.254
      Trying 192.168.0.254...
      Connected to 192.168.0.254.
      Escape character is '^]'.

      User Access Verification

      Password:
      telnet> q
      Connection closed.
      root@ debian:/home/user1/ops/adverse/adverse-1r/rocem

2. Smoke test of HG install

   1. Setup Flux nodes
   2. Established Seeds traffic - on Seeds host, manually set proxy and then authenticated once manually. Then kicked off ARP, DNS Domain Name System and HTTPS Hypertext Transfer Protocol Secure seeds.
   3. Set ROCEM
   4. IAC attacked - rcvd acceptable error codes
   5. Uploaded HG - via 3 flux nodes, this takes a while even with interpacket delay set to 0
   6. Unset ROCEM
   7. Had to chmod 755 on adverse-1h.txt file - it was read only when I tried to edit even as root. permissions were read and execute only.
   8. Established CT Counter Terrorism session through flux

   9. Verified DNS Domain Name System checkin is enabled - time to check in 2d 23h 29m 58s

   10. Verified DNS Domain Name System checkin commands available

   11. Disabled SDC Microsoft software packaging format and changed dns checkin delay to 60s, dns checkin variance to 10s for testing purposes

   12. Verified that DNS Domain Name System checkin is successful

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 0m 35s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 1m 0s
       Variance 0d 0h 0m 10s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 957
       Lifetime failure count 0
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       [checkin show]

   13. Enabled SDC Microsoft software packaging format with 12 hour time frame, however DNS Domain Name System checkins did not work. Attempted to web browse from Seeds host to give HG some traffic, however it still didn't work.

   14. Disabled SDC Microsoft software packaging format again and DNS Domain Name System checkins did not resume
   15. Had to disable and then re-enable dns checkin to get dns checkins to resume
   16. Re-enabled SDC, then bounced dns checkin service.
   17. DNS checkin did not resume. Will continue with SDC Microsoft software packaging format testing later, disabling at this time
   18. Changed the cname to time on X.X.X.X (LVLT-GOGL-8-8-8[US]) and restarted bind service.
   19. Due to positive response caching on the Flux2 BIND DNS server software server, had to change the positive response cache ttl to 300s on that server and restart bind service
   20. At next DNS Domain Name System checkin, cname time was used and the commands were executed reset failsafe, change variance to 0, change sdc to 1 hour, and change delay to 25 hours.
   21. Changed cname back loc1 on X.X.X.X (LVLT-GOGL-8-8-8[US]). Verified new caching settings are taking effect - after 300s, Flux2 BIND DNS server software sent the query to 4.4.4.4.
   22. Changed max-cache-ttl on 4.4.4.4 as well as flux2/BIND to 30s.
   23. Changed cname to loc3 and restarted bind9 on X.X.X.X (LVLT-GOGL-8-8-8[US]).
   24. At next checkin, the new loc3 commands were executed:

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled Yes
       Explicit Parameters Enabled No
       Time to Next Check-In 15d 7h 40m 43s
       Initial Delay 3d 0h 0m 0s
       Delay 15d 0h 0m 0s
       Variance 0d 12h 0m 0s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 12h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_map1_changedelay15d.cmd
       Lifetime success count 994
       Lifetime failure count 1
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error DNS Domain Name System Comms Failure (101)
       Time Since Last Error 0d 0h 1m 4s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       [checkin show]

3. On-Device Opsec
   1. With persistent HG still installed, running successfully after a reboot, CT Counter Terrorism session established - collected show tech - 3560G-showtech-with-persisted-HG
   2. Used device uninstall-g -mp -f to uninstall HG - waited 4 minutes, collected show tech - 3560G-showtech-afterHGuninstall
   3. Reloaded 3560G - collected another show tech - 3560G-showtech-afer-reload
   4. Re-installed HG - collected a show tech without CT Counter Terrorism session, before any reload to verify persistence - 3560G-showtech-withHG
   5. Uninstalled via DNS Domain Name System checkin - observed anomalous output in show stacks. Did not observe this after HG uninstall from CT Counter Terrorism session.
   6. Notes - Observed EAR Enterprise Archive 5012 - LOTS of blank lines in show stack after HG uninstall via DNS Domain Name System checkin++++++
      1. Also observed Init process missing after HG install - this is known issue - EAR Enterprise Archive 5163
      2. TCP Command process running - verified that this does show up at times without HG as well
      3. Need to verify sw forwarding counter in show controller output - EAR Enterprise Archive 5078 - validated that this value is not incrementing with install of HG
      4. About 2M additional memory used while HG installed.
   7. Further checking into show stacks output - installed HG and allowing some DNS Domain Name System checkins to go through. Will see if number of DNS Domain Name System checkins correlates to amount of blank likes in show stacks output.
   8. Allowed 23 DNS Domain Name System checkins to go through, then uninstalled via DNS Domain Name System checkin:
      1. Collected show tech - 3560G-showtech-afterHGuinstall-viaDNS
   9. Reloaded device, reinstalled HG, Allowed 23 DNS Domain Name System checkins to go through, then uninstalled via CT Counter Terrorism command
      1. Collected show tech - 3560G-showtech-afterHGuinstall-viaCT
      2. Noticed that blank lines are still present when uninstalled via CT Counter Terrorism - same number of blank lines as for previous test.
   10. Allow more DNS Domain Name System checkins to occur and see if the number of blank lines increases - number of blank lines is the same
       1. Allowed 46 checkins, then uninstalled via CT Counter Terrorism - collected show tech 3560G-showtech-afterHGuinstall-viaCT-46
   11. Verifying show controllers output after HG install:
       1. Started with a clean device - it had been running all weekend - sw forwarding counter is 4
       2. Set ROCEM, IAC International Access Code attacked, unset rocem - controllers counters still at 4
       3. Uploaded HG -
4. Tested Deaman failsafe where no hosts are available in snooped host list
   1. Installed HG and established CT Counter Terrorism session
   2. Changed DNS Domain Name System checkin settings to disable SDC, delay to be 20s, variance 10s.
   3. Allowed DNS Domain Name System checkins to fail - no snooped hosts in DNS Domain Name System client list.
   4. When the 12th failure occured, HG uninstalled:

      [192.168.211.10]> checkin show
      [Success]

      DnsCheckin
      Enabled Yes
      SDC Microsoft software packaging format Enabled No
      Explicit Parameters Enabled No
      Time to Next Check-In 0d 0h 0m 3s
      Initial Delay 3d 0h 0m 0s
      Delay 0d 0h 0m 20s
      Variance 0d 0h 0m 10s
      Domain www.vesselwatcher.net
      SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
      SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
      Last Command File Executed N/A
      Lifetime success count 0
      Lifetime failure count 11
      Failsafe Max 12
      Current Failsafe Count 11
      Deadman Enabled Yes
      Last Error DNS Domain Name System Comms Failure (101)
      Time Since Last Error 0d 0h 0m 17s

      Explicit Parameters
      IP 0.0.0.0
      Subnet 0.0.0.0
      MAC Apple Operating System 00:00:00:00:00:00
      VLAN Virtual Local Area Network 0
      TTL Time To Live 0
      Next Hop MAC Apple Operating System 00:00:00:00:00:00
      Nameserver 0.0.0.0
      ************ Success ************
      [checkin show]

      [192.168.211.10]> [Remote Failure]
      ************ Remote Failure ************
      Connection to device lost!!
      >
      >

5. Ad hoc test - reload DUT Device Under Test during HG install
   1. Set rocem, iac attacked, unset rocem
   2. Reloaded Dut during remote upload at 24%
   3. No alerting messages appeared on console, DUT Device Under Test rebooted normally
   4. Subsequent attack and install successful
6. Test HG persistence
   1. Installed HG via normal CONOP
   2. Established a CT Counter Terrorism session with trigger seq set to 0. Verified snooped dns client and server list - 192.168.211.10 and 192.168.0.11 respectively.
   3. Before 30 minutes had gone by, rebooted DUT
   4. Attempted to re-establsih CT Counter Terrorism session - trigger unsuccessful
   5. Reset beacon seq to 0 and then successfully re-established comms
   6. The time to next checkin for DNS Domain Name System check not persist - before reboot time to next checkin was 2d 23h 32m 9s and after reboot it was 2d 23h 53m 6s.
   7. Rebooted after an hour and 15 minutes of uptime.... DNS Domain Name System checkin parameters had been changed.
   8. Checkin parameters remained changed - however the trigger seq went back to 0:

      [192.168.211.10]> checkin show
      [Success]

      DnsCheckin
      Enabled Yes
      SDC Microsoft software packaging format Enabled Yes
      Explicit Parameters Enabled No
      Time to Next Check-In 0d 0h 0m 52s
      Initial Delay 3d 0h 0m 0s
      Delay 0d 0h 2m 0s
      Variance 0d 0h 0m 10s
      Domain www.vesselwatcher.net
      SDC Microsoft software packaging format Time Interval 0d 12h 0m 0s
      SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
      Last Command File Executed ci_loc1_resetfailsafe.cmd
      Lifetime success count 16
      Lifetime failure count 0
      Failsafe Max 12
      Current Failsafe Count 0
      Deadman Enabled Yes
      Last Error None (0)
      Time Since Last Error 0d 0h 0m 0s

      Explicit Parameters
      IP 0.0.0.0
      Subnet 0.0.0.0
      MAC Apple Operating System 00:00:00:00:00:00
      VLAN Virtual Local Area Network 0
      TTL Time To Live 0
      Next Hop MAC Apple Operating System 00:00:00:00:00:00
      Nameserver 0.0.0.0
      ************ Success ************
      [checkin show]

7. SDC test
   1. Established a CT Counter Terrorism session and changed delay to 60s and variance to 10s. While CT Counter Terrorism session was active, checkin time arrived and expired. I logged out from CT Counter Terrorism to see if it would snoop when CT Counter Terrorism session was not active and subsequesntly make a query via SDC Microsoft software packaging format but it did not.
   2. Established CT Counter Terrorism session and changed dns checkin delay to 2m and variance to 10s. Logged out from CT Counter Terrorism session and waited - after 2m I did rx a vesselwatcher query.
   3. Time between first DNS Domain Name System query and second query was about 3 minutes, however after that, they came in every two minutes:

      11:49:42.683220 IP 192.168.211.10.23165 > 192.168.0.11.domain: 7111+ A? www.vesselwatcher.net. (39)
      11:49:42.683967 IP 192.168.0.11.63256 > 4.4.4.4.domain: 24177+ [1au] A? www.vesselwatcher.net. (50)
      11:49:42.688779 IP 4.4.4.4.domain > 192.168.0.11.63256: 24177 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      11:49:42.689413 IP 192.168.0.11.60372 > 4.4.4.4.domain: 16280+ [1au] A? loc1.vesselwatcher.net. (51)
      11:49:42.690591 IP 192.168.0.11.domain > 192.168.211.10.23165: 7111 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      11:52:43.393058 IP 192.168.211.10.15926 > 192.168.0.11.domain: 40981+ A? www.vesselwatcher.net. (39)
      11:52:43.393700 IP 192.168.0.11.14071 > 4.4.4.4.domain: 60394+ [1au] A? www.vesselwatcher.net. (50)
      11:52:43.398762 IP 4.4.4.4.domain > 192.168.0.11.14071: 60394 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      11:52:43.399531 IP 192.168.0.11.18620 > 4.4.4.4.domain: 948+ [1au] A? loc1.vesselwatcher.net. (51)
      11:52:43.400846 IP 192.168.0.11.domain > 192.168.211.10.15926: 40981 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      11:54:48.874360 IP 192.168.211.10.20620 > 192.168.0.11.domain: 55646+ A? www.vesselwatcher.net. (39)
      11:54:48.875302 IP 192.168.0.11.47838 > 4.4.4.4.domain: 9865+ [1au] A? www.vesselwatcher.net. (50)
      11:54:48.879270 IP 4.4.4.4.domain > 192.168.0.11.47838: 9865 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      11:54:48.880038 IP 192.168.0.11.61522 > 4.4.4.4.domain: 48713+ [1au] A? loc1.vesselwatcher.net. (51)
      11:54:48.881292 IP 192.168.0.11.domain > 192.168.211.10.20620: 55646 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      11:56:59.349407 IP 192.168.211.10.16304 > 192.168.0.11.domain: 47923+ A? www.vesselwatcher.net. (39)
      11:56:59.350063 IP 192.168.0.11.9121 > 4.4.4.4.domain: 20606+ [1au] A? www.vesselwatcher.net. (50)
      11:56:59.354573 IP 4.4.4.4.domain > 192.168.0.11.9121: 20606 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      11:56:59.355361 IP 192.168.0.11.5131 > 4.4.4.4.domain: 18376+ [1au] A? loc1.vesselwatcher.net. (51)
      11:56:59.356677 IP 192.168.0.11.domain > 192.168.211.10.16304: 47923 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)

   4. Checked on Seeds traffic for any punch through DNS Domain Name System packets or replies - did not see anything come on wireshark during DNS Domain Name System checkin.
   5. Disabled HTTPS Hypertext Transfer Protocol Secure and ARP Address Resolution Protocol seeds on on seeds host and allowed DNS Domain Name System seeds to continue - did not see the next checkin. DNS seeds is not enough for SDC Microsoft software packaging format apparently.
   6. Restarted HTTPS Hypertext Transfer Protocol Secure and ARP Address Resolution Protocol seeds - about 4 minutes later I did get a DNS Domain Name System checkin again:

      12:13:17.519037 IP 192.168.211.10.13372 > 192.168.0.11.domain: 31060+ A? www.vesselwatcher.net. (39)
      12:13:17.519933 IP 192.168.0.11.9343 > 4.4.4.4.domain: 57259+ [1au] A? www.vesselwatcher.net. (50)
      12:13:17.524538 IP 4.4.4.4.domain > 192.168.0.11.9343: 57259 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:13:17.525289 IP 192.168.0.11.57649 > 4.4.4.4.domain: 41926+ [1au] A? loc1.vesselwatcher.net. (51)
      12:13:17.526452 IP 192.168.0.11.domain > 192.168.211.10.13372: 31060 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      12:17:23.277763 IP 192.168.211.10.10608 > 192.168.0.11.domain: 41738+ A? www.vesselwatcher.net. (39)
      12:17:23.278454 IP 192.168.0.11.41021 > 4.4.4.4.domain: 23973+ [1au] A? www.vesselwatcher.net. (50)
      12:17:23.283150 IP 4.4.4.4.domain > 192.168.0.11.41021: 23973 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:17:23.283778 IP 192.168.0.11.6542 > 4.4.4.4.domain: 17025+ [1au] A? loc1.vesselwatcher.net. (51)
      12:17:23.284924 IP 192.168.0.11.domain > 192.168.211.10.10608: 41738 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      12:20:58.924137 IP 192.168.211.10.29641 > 192.168.0.11.domain: 30681+ A? www.vesselwatcher.net. (39)
      12:20:58.924853 IP 192.168.0.11.62419 > 4.4.4.4.domain: 34273+ [1au] A? www.vesselwatcher.net. (50)
      12:20:58.929699 IP 4.4.4.4.domain > 192.168.0.11.62419: 34273 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:20:58.930630 IP 192.168.0.11.10872 > 4.4.4.4.domain: 692+ [1au] A? loc1.vesselwatcher.net. (51)
      12:20:58.932027 IP 192.168.0.11.domain > 192.168.211.10.29641: 30681 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      12:24:24.585459 IP 192.168.211.10.13467 > 192.168.0.11.domain: 40913+ A? www.vesselwatcher.net. (39)
      12:24:24.586113 IP 192.168.0.11.29376 > 4.4.4.4.domain: 50225+ [1au] A? www.vesselwatcher.net. (50)
      12:24:24.591288 IP 4.4.4.4.domain > 192.168.0.11.29376: 50225 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:24:24.591859 IP 192.168.0.11.11661 > 4.4.4.4.domain: 63214+ [1au] A? loc1.vesselwatcher.net. (51)
      12:24:24.593216 IP 192.168.0.11.domain > 192.168.211.10.13467: 40913 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      12:27:55.346378 IP 192.168.211.10.29132 > 192.168.0.11.domain: 21644+ A? www.vesselwatcher.net. (39)
      12:27:55.347169 IP 192.168.0.11.3441 > 4.4.4.4.domain: 46765+ [1au] A? www.vesselwatcher.net. (50)
      12:27:55.351935 IP 4.4.4.4.domain > 192.168.0.11.3441: 46765 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:27:55.352804 IP 192.168.0.11.27175 > 4.4.4.4.domain: 34112+ [1au] A? loc1.vesselwatcher.net. (51)
      12:27:55.354245 IP 192.168.0.11.domain > 192.168.211.10.29132: 21644 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      12:31:00.834970 IP 192.168.211.10.8719 > 192.168.0.11.domain: 51184+ A? www.vesselwatcher.net. (39)
      12:31:00.835853 IP 192.168.0.11.63238 > 4.4.4.4.domain: 17530+ [1au] A? www.vesselwatcher.net. (50)
      12:31:00.840680 IP 4.4.4.4.domain > 192.168.0.11.63238: 17530 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:31:00.841358 IP 192.168.0.11.43756 > 4.4.4.4.domain: 61869+ [1au] A? loc1.vesselwatcher.net. (51)
      12:31:00.842577 IP 192.168.0.11.domain > 192.168.211.10.8719: 51184 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)

      12:34:46.651969 IP 192.168.0.11.51319 > 4.4.4.4.domain: 63821+ [1au] A? www.vesselwatcher.net. (50)
      12:34:46.656434 IP 4.4.4.4.domain > 192.168.0.11.51319: 63821 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      12:34:46.657161 IP 192.168.0.11.30791 > 4.4.4.4.domain: 50251+ [1au] A? loc1.vesselwatcher.net. (51)
      12:34:46.658276 IP 192.168.0.11.domain > 192.168.211.10.19233: 1003 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)

      12:34:46.651231 IP 192.168.211.10.19233 > 192.168.0.11.domain: 1003+ A? www.vesselwatcher.net. (39)

   7. No failures have incremented:

      [192.168.211.10]> checkin show
      [Success]

      DnsCheckin
      Enabled Yes
      SDC Microsoft software packaging format Enabled Yes
      Explicit Parameters Enabled No
      Time to Next Check-In 0d 0h 1m 11s
      Initial Delay 3d 0h 0m 0s
      Delay 0d 0h 2m 0s
      Variance 0d 0h 0m 10s
      Domain www.vesselwatcher.net
      SDC Microsoft software packaging format Time Interval 0d 12h 0m 0s
      SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
      Last Command File Executed ci_loc1_resetfailsafe.cmd
      Lifetime success count 12
      Lifetime failure count 0
      Failsafe Max 12
      Current Failsafe Count 0
      Deadman Enabled Yes
      Last Error None (0)
      Time Since Last Error 0d 0h 0m 0s

      Explicit Parameters
      IP 0.0.0.0
      Subnet 0.0.0.0
      MAC Apple Operating System 00:00:00:00:00:00
      VLAN Virtual Local Area Network 0
      TTL Time To Live 0
      Next Hop MAC Apple Operating System 00:00:00:00:00:00
      Nameserver 0.0.0.0

   8. SDC comms are working, however it seems to take longer than just the checkin delay +/- variance to get checkins. Extra time spent snooping - snooping is set to on for 60s, then off for 10s. Snoop is set this way for dns, web and comms, and https.

8. Configured DNS Domain Name System server as Proxyy server
   1. DNS checkins have resumed after the change

      16:45:16.872516 IP 192.168.211.10.26768 > 192.168.0.11.domain: 26686+ A? www.vesselwatcher.net. (39)
      16:45:16.873797 IP 192.168.0.11.63579 > 192.168.0.4.domain: 34834+ [1au] A? www.vesselwatcher.net. (50)
      16:45:16.882154 IP 192.168.0.4.domain > 192.168.0.11.63579: 34834 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      16:45:16.883501 IP 192.168.0.11.33273 > 192.168.0.4.domain: 17156+ [1au] A? loc1.vesselwatcher.net. (51)
      16:45:16.884533 IP 192.168.0.11.domain > 192.168.211.10.26768: 26686 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
      16:51:28.204284 IP 192.168.211.10.21803 > 192.168.0.11.domain: 19945+ A? www.vesselwatcher.net. (39)
      16:51:28.204948 IP 192.168.0.11.50595 > 192.168.0.4.domain: 64097+ [1au] A? www.vesselwatcher.net. (50)
      16:51:28.211713 IP 192.168.0.4.domain > 192.168.0.11.50595: 64097 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
      16:51:28.212386 IP 192.168.0.11.8652 > 192.168.0.4.domain: 38988+ [1au] A? loc1.vesselwatcher.net. (51)
      16:51:28.213306 IP 192.168.0.11.domain > 192.168.211.10.21803: 19945 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)

9. Test failure case where DNS Domain Name System checkin does not get a response for its zone:

   1. Set checkin settings to delay 20s, variance 0s, sdc defaults
   2. Commented out the vesselwatcher.net zone
   3. Up to 8 failures

      DnsCheckin
      Enabled Yes
      SDC Microsoft software packaging format Enabled Yes
      Explicit Parameters Enabled No
      Time to Next Check-In 0d 0h 0m 0s
      Initial Delay 3d 0h 0m 0s
      Delay 0d 0h 0m 20s
      Variance 0d 0h 0m 0s
      Domain www.vesselwatcher.net
      SDC Microsoft software packaging format Time Interval 0d 12h 0m 0s
      SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
      Last Command File Executed ci_loc1_resetfailsafe.cmd
      Lifetime success count 34
      Lifetime failure count 8
      Failsafe Max 12
      Current Failsafe Count 8
      Deadman Enabled Yes
      Last Error DNS Domain Name System Comms Failure (101)
      Time Since Last Error 0d 0h 0m 36s

      Explicit Parameters
      IP 0.0.0.0
      Subnet 0.0.0.0
      MAC Apple Operating System 00:00:00:00:00:00
      VLAN Virtual Local Area Network 0
      TTL Time To Live 0
      Next Hop MAC Apple Operating System 00:00:00:00:00:00
      Nameserver 0.0.0.0
      ************ Success ************
      [checkin show]

   4. HG uninstalled after 12 failures

10. Ad-hoc test - reinstall HG after uninstall due to failsafe timeout
    1. Re-set ROCEM, IAC International Access Code attack, unset ROCEM
    2. used remote to upload HG
    3. Established CT Counter Terrorism session successfully - no errors on login. Normal IAC International Access Code attack spike to 32% on CPU.
11. Ad-hoc test - Rapid DNS Domain Name System checkin
    1. Installed HG and disabled SDC, set checkin delay to 20s and Variance to 1s
    2. Observed potential issue with changing these parameters - logged to file checkin-change-delay-issue
    3. Left running over night. In the morning, successfully reconnected to HG over CT Counter Terrorism session and verified checkin:

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 0m 6s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 0m 20s
       Variance 0d 0h 0m 1s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 2759
       Lifetime failure count 0
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       [checkin show]

       [192.168.211.10]>

12. Test reload of HG modules

    1. From CT Counter Terrorism session, performed module show
    2. Restart DnsCheckin module

       [192.168.211.10]> module stop DnsCheckin

       [Success]
       ************ Success ************
       [module stop DnsCheckin]

    3. module no longer shows up in module show, tab tab does not show checkin command module
    4. Started module

       [192.168.211.10]> module start DNSCheckin.mod
       [Success]
       ************ Success ************
       [module start DNSCheckin.mod]

    5. DnsCheckin 5 No Running 0x2c509bc default:DnsCheckin.mod

    6. DnsCheckin ModuleRunning 5 No

    7. Restarted module -

       [192.168.211.10]> module restart DNSCheckin.mod
       [Success]
       ************ Success ************
       [module restart DNSCheckin.mod]

       [192.168.211.10]>

    8. Parameters were retained through module restart:

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 0m 7s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 0m 20s
       Variance 0d 0h 0m 1s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 2794
       Lifetime failure count 0
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       Press <enter> to continue
       [checkin show]

    9. Stopped and started FilterBroker module
    10. Restarted FilterBroker - takes longer than DNSCheckin but succeeds
    11. Attempted to stop module Socket - but got message that this is crticial:

        [192.168.211.10]> module stop Socket
        [Remote Failure]
        "Unload Module" command error:
        [Beachhead 112] Cannot unload critical
        ************ Remote Failure ************
        [module stop Socket]

        [192.168.211.10]>

    12. Successfully stopped, started and then restarted ACEMod.mod

    13. CovertTunnel.mod - stopp ed, upon restart it didn't restart on the first try:

        [192.168.211.10]> module start default:CovertTunnel.mod
        [Remote Failure]
        "Load Module from File" command error:
        [Beachhead 103] Load module failed
        ************ Remote Failure ************
        [module start default:CovertTunnel.mod]

        [192.168.211.10]> module start default:CovertTunnel.mod
        [Success]
        ************ Success ************
        [module start default:CovertTunnel.mod]

        [192.168.211.10]> module show
        [Success]
        Name Version Boot Persistence State Address Path
        Beachhead 11 No Running 0x2460894 default:Beachhead.mod
        IV 17 No Running 0x26de184 default:IV.mod
        OS Operating System 23 No Running 0x29d8b98 default:OS.mod
        Utility 16 Yes Running 0x28b9b10 default:Utility.mod
        Process 31 Yes Running 0x29f2ad0 default:Process.mod
        Broker 17 Yes Running 0x2a6f584 default:Broker.mod
        SWINE 16 No Running 0x27500b4 default:SWINE.mod
        MiniLZO 6 Yes Running 0x274d944 default:MiniLZO.mod
        RC6 7 No Running 0x1b52f84 default:RC6.mod
        Configuration 7 Yes Running 0x2b9001c default:Configuration.mod
        Packet 35 Yes Running 0x2a1423c default:Packet.mod
        EBroker 8 No Running 0x2802120 default:EBroker.mod
        Device 31 Yes Running 0x2455d68 default:Device.mod
        Beacon 21 Yes Running 0x2952028 default:Beacon.mod
        Socket 19 Yes Running 0x28f913c default:Socket.mod
        Trigger 22 Yes Running 0x2a7c604 default:Trigger.mod
        DNS Domain Name System 19 No Running 0x286f798 default:DNS.mod
        HTTPS Hypertext Transfer Protocol Secure 18 No Running 0x28d909c default:HTTPS.mod
        Web 4 Yes Running 0x2ac5d58 default:Web.mod
        Persistence 1 Yes Running 0x28e1d70 default:Persistence.mod
        Uninstall 4 Yes Running 0x28e4688 default:Uninstall.mod
        CFS 19 No Running 0x2878a04 default:CFS.mod
        DnsCheckin 5 No Running 0x2c52158 default:DnsCheckin.mod
        FilterBroker 22 Yes Running 0x2aaa114 default:FilterBroker.mod
        ACE Application Control Engine (Module) 26 No Running 0x2a04f28 default:ACE.mod
        Tunnel 10 No Running 0x2a994b4 default:Tunnel.mod
        Name State Version Critical
        Beachhead ModuleRunning 11 Yes
        IV ModuleRunning 17 Yes
        Press <enter> to continue

        OS ModuleRunning 23 Yes
        Utility ModuleRunning 16 Yes
        Process ModuleRunning 31 Yes
        Broker ModuleRunning 17 Yes
        SWINE ModuleRunning 16 Yes
        MiniLZO ModuleRunning 6 Yes
        RC6 ModuleRunning 7 Yes
        Configuration ModuleRunning 7 Yes
        Packet ModuleRunning 35 Yes
        EBroker ModuleRunning 8 Yes
        Device ModuleRunning 31 Yes
        Beacon ModuleRunning 21 Yes
        Socket ModuleRunning 19 Yes
        Trigger ModuleRunning 22 No
        DNS Domain Name System ModuleRunning 19 Yes
        HTTPS Hypertext Transfer Protocol Secure ModuleRunning 18 Yes
        Web ModuleRunning 4 Yes
        Persistence ModuleRunning 1 No
        Uninstall ModuleRunning 4 No
        CFS ModuleRunning 19 Yes
        DnsCheckin ModuleRunning 5 No
        FilterBroker ModuleRunning 22 No
        ACE Application Control Engine (Module) ModuleRunning 26 No
        Tunnel ModuleRunning 10 No
        ************ Success ************
        [module show]

    14. Restarted tunnel module successfully

    15. After further testing, this module does restart successfully if you want for the module to disappear from the output of module show. For some time it will just say module stopped. Attempts to start the module during this time will fail. Once it drops completely from the output of module show, attempts to start the module are successful.
13. Ad Hoc - Stop Checkin Module, reload DUT
    1. DUT had been running HG all night.
    2. Connected over an hour ago with CT Counter Terrorism session
    3. Checkin module stopped
    4. Reloaded DUT Device Under Test - DNS Domain Name System checkin module started up on reload - EAR Enterprise Archive 2036
    5. Checkin parameters were persisted
    6. Trigger sequence number reverted to 1, which was the last successful trigger sequence from this morning. So the most recent trigger seq had not yet been persisted.
    7. Changed delay to 10m and variance to 10s. Allowed time to checkin to count down to 3:30. Reloaded DUT
    8. Before reload

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 3m 42s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 10m 0s
       Variance 0d 0h 0m 10s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 3088
       Lifetime failure count 2
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error DNS Domain Name System Comms Failure (101)
       Time Since Last Error 0d 1h 14m 56s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       Press <enter> to continue
       [checkin show]

    9. After reload

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 6m 7s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 10m 0s
       Variance 0d 0h 0m 10s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed N/A
       Lifetime success count 3088
       Lifetime failure count 2
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

       Explicit Parameters
       IP 0.0.0.0
       Subnet 0.0.0.0
       MAC Apple Operating System 00:00:00:00:00:00
       VLAN Virtual Local Area Network 0
       TTL Time To Live 0
       Next Hop MAC Apple Operating System 00:00:00:00:00:00
       Nameserver 0.0.0.0
       ************ Success ************
       Press <enter> to continue
       [checkin show]

       The delay and variance updates were persisted, SDC Microsoft software packaging format being disabled was persisted, however the time to next check-in was not persisted.

14. SDC Test - SDC Microsoft software packaging format changes persisted
    1. Currently SDC Microsoft software packaging format is disabled
    2. SDC disabled already survived one reload
    3. Enabled SDC:

       SDC Enabled Yes

       SDC Time Interval 0d 10h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 10m 0s

    4. Reloaded device

    5. SDC changes were persisted:

       SDC Enabled Yes

       SDC Time Interval 0d 10h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 10m 0s

15. Test SDC Microsoft software packaging format window expiring
    1. Changed SDC Microsoft software packaging format params to 2m window, 0s max existing host age
    2. changed delay to 30s, var to 10s

    3. [192.168.211.10]> dns get_snooped_host_list_client 0 0
       [Pending]
       Job: 136269224
       ************ Pending ************
       [dns get_snooped_host_list_client 0 0]

       [192.168.211.10]> [Success]

       IP Address MAC Apple Operating System Addr VLAN Virtual Local Area Network TTL Time To Live Count Resolver IP Status

       192.168.211.10 00:14:A8:48:07:C0 1 128 121 192.168.0.11 GOOD
       Received 1 entries.

       Job: 136269224
       ************ Success ************

       [192.168.211.10]>

    4. Maintained a CT Counter Terrorism session to prevent snooping for SDC
    5. After time to checkin had reached zero, waited 2 minutes, then did rx a checkin - expected interval - 2.5 minutes

       13:28:05.984975 IP 192.168.211.10.13765 > 192.168.0.11.domain: 33717+ A? www.vesselwatcher.net. (39)
       13:28:05.985614 IP 192.168.0.11.16951 > 192.168.0.4.domain: 12025+ [1au] A? www.vesselwatcher.net. (50)
       13:28:05.992488 IP 192.168.0.4.domain > 192.168.0.11.16951: 12025 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
       13:28:05.993159 IP 192.168.0.11.60671 > 192.168.0.4.domain: 15231+ [1au] A? loc1.vesselwatcher.net. (51)
       13:28:05.994096 IP 192.168.0.11.domain > 192.168.211.10.13765: 33717 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)
       13:30:32.625235 IP 192.168.211.10.16297 > 192.168.0.11.domain: 24261+ A? www.vesselwatcher.net. (39)
       13:30:32.625866 IP 192.168.0.11.16244 > 192.168.0.4.domain: 9574+ [1au] A? www.vesselwatcher.net. (50)
       13:30:32.631881 IP 192.168.0.4.domain > 192.168.0.11.16244: 9574 2/1/2 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (119)
       13:30:32.632365 IP 192.168.0.11.47097 > 192.168.0.4.domain: 52576+ [1au] A? loc1.vesselwatcher.net. (51)
       13:30:32.633351 IP 192.168.0.11.domain > 192.168.211.10.16297: 24261 2/1/1 CNAME loc1.vesselwatcher.net., A XX.X.X.X (FINET[US]) (108)

    6. Cleared dns snooping stats - watched and a failure did increment:

       Lifetime failure count 3

       Current Failsafe Count 1

    7. Exited CT Counter Terrorism session to allow snooping to occur again
    8. Logged back in after about 2 minutes
    9. Current failsafe count back to 0, lifetime failsafes still at 3.
    10. DNS has once again snooped a client
16. Confirm issue with change checkin delay
    1. Confirmed not to be an issue - best practice when changing both variance and delay would be to change variance first so that the time to next checkin value is updated with new variance
17. Test failure where DNS Domain Name System responds but without a CNAME
    1. With HG running and DNS Domain Name System checking in every 60seconds
    2. SDC disabled - CT Counter Terrorism session active
    3. IXIA running background traffic
    4. Verified DNS Domain Name System checkins are successfu
    5. Updated BIND DNS Domain Name System server software on X.X.X.X (LVLT-GOGL-8-8-8[US]) to remove CNAME from zone
    6. When no CNAME is rx, it counts as a DNS Domain Name System Checkin success. Failure does not increment.
    7. Let this run with and without CT Counter Terrorism session

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 0m 56s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 1m 0s
       Variance 0d 0h 0m 0s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 3275
       Lifetime failure count 20
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error DNS Domain Name System Comms Failure (101)
       Time Since Last Error 0d 0h 37m 19s

18. Test failure where DNS Domain Name System completely timesout, no response either way
    1. SDC disabled on checkin
    2. Verified Seeds traffic running
    3. Stopped bind service on flux2 - verified Seeds can no longer resolve
    4. Verified that HG has the Seeds host already in dns snooped host list
    5. Started TCP Transport Control Protocol dump on flux 2 to verify DNS Domain Name System checkin attempts and lack of reply
    6. Change variance to 1s and then change delay to 30s
    7. Verified that HG attempts to do a dns checkin and receives no response - tries 3x with 32s between each try before counting it as a failed attempt
    8. Actually, Flux2 sends an ICMP Internet Control Message Protocol unreachable back to HG, but HG does not pick it up, it goes through to the impersonated host. - HG-7
    9. Restarted bind 9 after allowing 6 failures to accumulate
    10. HG successfully checked in and now current failsafe count is back to 0.
    11. To verify negative replies are not punching through, commenting out HG vesselwatcher zone on X.X.X.X (LVLT-GOGL-8-8-8[US]) and restarting bind.
    12. Negative replies do not punch through to the impersonated host and are rcvd in 10 seconds. After the negative response is received, HG then restarts the time to check in per the delay parameter and will send another request in that time.
    13. Shutdown BIND DNS Domain Name System server software on 4.4.4.4 - 192.168.0.11 replies to HG with SERVER FAIL and it does not punch through to impersonated host.
    14. Tried shutting down interface eth0 on 192.168.0.11 - nothing punched through to impersonated host
19. Persistence test - Verify if time to next checkin is persisted
    1. On reloads after changes made only a short time ago, trigger seq and time to next checkin are not persisted. Once more time has passed, trigger seq is persisted.
    2. Need to verify if this is also true for time to next checkin
    3. Set checkin delay to 10d with variance of 0.
    4. Verified that time to next check said 10d.
    5. Allowed HG to run over night
    6. the next day, verified that time to next checkin had decremented:

       [192.168.211.10]> checkin show
       [Success]

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 9d 6h 45m 8s
       Initial Delay 3d 0h 0m 0s
       Delay 10d 0h 0m 0s
       Variance 0d 0h 0m 0s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 3230
       Lifetime failure count 17
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error DNS Domain Name System Comms Failure (101)
       Time Since Last Error 0d 18h 22m 58s

    7. Current trigger seq number is 5

    8. Reloaded DUT Device Under Test and time to next checkin was persisted although not up to the mnute, and trigger seq was persisted:

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 9d 7h 4m 33s
       Initial Delay 3d 0h 0m 0s
       Delay 10d 0h 0m 0s
       Variance 0d 0h 0m 0s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed N/A
       Lifetime success count 3230
       Lifetime failure count 17
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

20. Ad hoc test - power failure

    1. with HG installed, pulled power out back of DUT
    2. This was checkin show before:

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 9d 5h 48m 41s
       Initial Delay 3d 0h 0m 0s
       Delay 10d 0h 0m 0s
       Variance 0d 0h 0m 0s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed N/A
       Lifetime success count 3230
       Lifetime failure count 17
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error None (0)
       Time Since Last Error 0d 0h 0m 0s

    3. Values reverted back to what they were this morning - seq numnber 5 as well as next time to checkin.

    4. No messages printed to console
21. Test of DNS Domain Name System checkin cname commands
    1. With SDC Microsoft software packaging format disabled, IXIA running, and CT Counter Terrorism session active, verified DNS Domain Name System Checkin currently working with the following params:

       DnsCheckin
       Enabled Yes
       SDC Microsoft software packaging format Enabled No
       Explicit Parameters Enabled No
       Time to Next Check-In 0d 0h 0m 9s
       Initial Delay 3d 0h 0m 0s
       Delay 0d 0h 1m 0s
       Variance 0d 0h 0m 4s
       Domain www.vesselwatcher.net
       SDC Microsoft software packaging format Time Interval 0d 0h 0m 0s
       SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
       Last Command File Executed ci_loc1_resetfailsafe.cmd
       Lifetime success count 3311
       Lifetime failure count 20
       Failsafe Max 12
       Current Failsafe Count 0
       Deadman Enabled Yes
       Last Error DNS Domain Name System Comms Failure (101)
       Time Since Last Error 0d 1h 14m 27s

    2. time - changed cname to time
       1. executed as expected - reset failsafe, changed sdc window ( plus enabled SDC Microsoft software packaging format in doing so), changed variance and delay:

          DnsCheckin
          Enabled Yes
          SDC Microsoft software packaging format Enabled Yes
          Explicit Parameters Enabled No
          Time to Next Check-In 1d 0h 55m 2s
          Initial Delay 3d 0h 0m 0s
          Delay 1d 1h 0m 0s
          Variance 0d 0h 0m 0s
          Domain www.vesselwatcher.net
          SDC Microsoft software packaging format Time Interval 0d 1h 0m 0s
          SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
          Last Command File Executed changedelay25h.cmd
          Lifetime success count 3314
          Lifetime failure count 20
          Failsafe Max 12
          Current Failsafe Count 0
          Deadman Enabled Yes
          Last Error DNS Domain Name System Comms Failure (101)
          Time Since Last Error 0d 1h 21m 31s

    3. Changed CNAME back to loc3 and reset variance and delay to 5s and 60s respectively, exited CT Counter Terrorism session

       1. executed as expected - reset failsafe, changed sdc window, change variance, change delay

          DnsCheckin
          Enabled Yes
          SDC Microsoft software packaging format Enabled Yes
          Explicit Parameters Enabled No
          Time to Next Check-In 14d 14h 30m 13s
          Initial Delay 3d 0h 0m 0s
          Delay 15d 0h 0m 0s
          Variance 0d 12h 0m 0s
          Domain www.vesselwatcher.net
          SDC Microsoft software packaging format Time Interval 0d 12h 0m 0s
          SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
          Last Command File Executed ci_map1_changedelay15d.cmd
          Lifetime success count 3315
          Lifetime failure count 20
          Failsafe Max 12
          Current Failsafe Count 0
          Deadman Enabled Yes
          Last Error DNS Domain Name System Comms Failure (101)
          Time Since Last Error 0d 1h 37m 25s

    4. Changed CNAME back to time and reset variance and delay to 5s and 60s respectively, exited CT Counter Terrorism session

       1. Executed as expected:

          DnsCheckin
          Enabled Yes
          SDC Microsoft software packaging format Enabled Yes
          Explicit Parameters Enabled No
          Time to Next Check-In 1d 0h 59m 30s
          Initial Delay 3d 0h 0m 0s
          Delay 1d 1h 0m 0s
          Variance 0d 0h 0m 0s
          Domain www.vesselwatcher.net
          SDC Microsoft software packaging format Time Interval 0d 1h 0m 0s
          SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
          Last Command File Executed changedelay25h.cmd
          Lifetime success count 3316
          Lifetime failure count 20
          Failsafe Max 12
          Current Failsafe Count 0
          Deadman Enabled Yes
          Last Error DNS Domain Name System Comms Failure (101)
          Time Since Last Error 0d 1h 47m 19s

    5. Testing callback once a day = info
       1. Setup a second ICON VM Virtual Machine for HG to call back to - 172.20.12.36
       2. Set HG to call in every 60s, no variance, SDC Microsoft software packaging format window 1 hour, SDC Microsoft software packaging format enabled

          DnsCheckin
          Enabled Yes
          SDC Microsoft software packaging format Enabled Yes
          Explicit Parameters Enabled No
          Time to Next Check-In 0d 0h 0m 17s
          Initial Delay 3d 0h 0m 0s
          Delay 0d 0h 1m 0s
          Variance 0d 0h 0m 0s
          Domain www.vesselwatcher.net
          SDC Microsoft software packaging format Time Interval 0d 1h 0m 0s
          SDC Microsoft software packaging format Max Existing Host Age 0d 0h 0m 0s
          Last Command File Executed ci_loc1_resetfailsafe.cmd
          Lifetime success count 3317
          Lifetime failure count 20
          Failsafe Max 12
          Current Failsafe Count 0
          Deadman Enabled Yes
          Last Error DNS Domain Name System Comms Failure (101)
          Time Since Last Error 0d 3h 2m 18s

       3. Changed CNAME to info and set up listening window on ICON2

       4. Having a lot of trouble - HG not calling back to second ICON machine as far as I can tell. Trigger is successful, no call back attempt seen in wireshark on port mirror VM, mirroring proxy eth1.
       5. After troubleshooting, found at least one issue - when Seeds traffic only includes https requests to 8088, and https get_snooped_host_list_client has been cleared, HG does not detect any HTTPS Hypertext Transfer Protocol Secure clients to use for the connection. HG-9 created for this issue. Explicit params can be used to establish CT Counter Terrorism session in this case to internal flux node, however per User #77275/Xetron, explicit params will not work to callback to an external IP address. User #77276/Xetron going to research changing the port number HG uses to locate HTTPS Hypertext Transfer Protocol Secure traffic to snoop and get back with me.
22. Test 3 day initial delay
    1. I had installed HG on Friday and let it run over the weekend
    2. Did not make any changes to checkin paramters
    3. On Monday, after the three day initial delay expired, HG did successfully checkin via DNS Domain Name System Checkin and got CNAME loc1.
23. Test unexpected CNAME
    1. Changed cname to foo to test unexpected CNAME
    2. Changed DNS Domain Name System checkin params to no varaince, delay 10s, no SDC
    3. Observed DNS Domain Name System chekcin and CNAME response of foo on X.X.X.X (LVLT-GOGL-8-8-8[US])
    4. Checkin show on HG implant counts these as successfull check ins.
    5. Multiple CNAMES not possible.
24. Test DNS Domain Name System Checkin SMITE rules
    1. Changed DNS Domain Name System checkin delay to 1m
    2. Changed DNS Domain Name System CNAME to map2 to test SMITE rules
    3. DNS successfully checked in - smite rules were created
    4. Found that SMITE rule kept firing because I didn't change the DNS Domain Name System CNAME
    5. The rules were successfully deleted and recreated each time the DNSCheckin occured, rule numbers incrementing
    6. Ran the tanker CNAME to delete the rules
    7. Ran the map2 CNAME again and this time reverted to loc1 after the checkin occured only one time
    8. Ran loc2 with a private IP as a response and noted that it causes a failure to increment
    9. Responses with 1918 space cause a failure to increment - deadman scenario
    10. Toggled between loc2, loc1, map2 and tanker rules - no issues, rules behaved as expected
    11. Tested map1 command to change delay to 15d
25. SMITE Test
    1. Setup a windows victim on Seeds vlan
    2. Rules will likely not work since they reference port 80, clients on this network use 8088
26. Test of Ability to call back externally - HG-10
    1. In earlier testing, have had intermittent problems calling back to an external IP address to make a CT Counter Terrorism connection.
    2. Xetron sent me a debug version of HG, which I installed and collected output from for their analysis
    3. User #77277/Xetron called to say they believe this is an HG bug and they are looking into it further.
    4. Xetron created EAR Enterprise Archive 5536 for this.

### Previous versions:

| 1 empty | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 [Xetron] | 11 [Xetron] | 12 [Xetron] | 13 [Xetron] | 14 [Xetron] | 15 [Xetron] | 16 [Xetron] | 17 [Xetron] | 18 [Xetron] | 19 [Xetron] | 20 [Xetron] | 21 [Xetron] | 22 [Xetron] | 23 [Xetron] | 24 [Xetron] | 25 [Xetron] | 26 [Xetron] | 27 [Xetron] |