Roll | Effect |
---|---|
2 | Skip next opponent’s turn (rare but powerful) |
3 | Move any ship up to 3 spaces |
4 | Repair 2 hits on any ship |
5 | Take a second shot this turn |
6 | Repair 1 hit |
7 | Standard turn (fire one shot) |
8 | Move a ship 1 space or rotate |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
The purpose of this document is to capture the configuration and setup to run Android on docker on a synology NAS. The purpose of running android is to capture and route notifications via MQTT.
- this is still not done
- I assume you've set up internet access to a VLAN presented to your docker network.
- VLAN 10, which carries subnet 192.168.10.0/24, is our target VLAN.
- Be serious in your delivery.
- Do not be jovial or excessively friendly with each other. And do not interject with casual items like "uh huh", "yea", "right", "okay". Just cut that completely out.
- Do not repeat items between speakers.
- Do not split sentences between speakers. Do NOT ignore this instruction.
- Be critical of the sources and form your own opinions, but identify them as your own.
- Dispute one point is a ridiculous fashion, but when you banter about it for about 30 seconds, have both of you identify the item as ridiculous.
- https://youtube.com/@campingwithsteve (personal experience camping)
- https://youtube.com/@WeirdExplorer (personal experience fruit/culture)
- https://youtube.com/@AlexRothman (history/culture)
- https://youtube.com/@PeterSantenello (investigative journalism about travel/cultures)
- https://youtube.com/@Azeal (interviews about human experiences (if you believe them))
- https://youtube.com/@HorsesOnYT (reflective cultural analysis)
- https://youtube.com/@justinmonarch (reflective self help philosophy)
- https://youtube.com/@NoBoilerplate (systematic self help)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#baseline_layer.json is exported layer from the navigator... there certainly is a way to create the json from scratch reviewing specs, but it was very fsat to just do this. | |
$sourcefile = ".attack nav layers\baseline_layer.json" | |
$offtechoutfile = ".\attack nav layers\offensive_techs.json" | |
$deftechoutfile = ".\attack nav layers\defensive_techs.json" | |
#goal here is to: | |
# define two att&ck navigator layer json files | |
# one is for offensive techniques |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$orcacomplianceframework = @" | |
Collection - Automated Collection - T1119 | |
Collection - Data from Cloud Storage - T1530 | |
Collection - Data from Information Repositories - T1213 | |
Collection - Data Staged - T1074 | |
Collection - Email Collection - T1114 | |
Credential Access - Brute Force - T1110 | |
Credential Access - Forge Web Credentials - T1606 | |
Credential Access - Modify Authentication Process - T1556 | |
Credential Access - Multi-Factor Authentication Request Generation - T1621 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# summary: | |
# Process ATT&CK and D3FEND data to indicate likelihood an ATT&CK technique is a choke point as defined in this article (https://medium.com/mitre-engenuity/where-to-begin-prioritizing-att-ck-techniques-c535b50983f4). This theory considers the following conjecture: MITRE will assign research hours to align with prioritization of offensive technique (resulting severity, frequency of observation, etc). This theory considers the following facts: ATT&CK procedure examples are well documented, D3FEND offensive blast radius is well documented. | |
# Remember to see "Limitations and future work" section of the above blog post/article. | |
# also see "BIASES WHEN MAPPING TO MITRE ATT&CK" section of (https://www.cisa.gov/uscert/sites/default/files/publications/Best%20Practices%20for%20MITRE%20ATTCK%20Mapping.pdf) | |
# this covers the following biases: Novelty bias, Visibility bias, Producer bias, Victim bias, Availability bias... | |
# you won't ever be able to eliminate these, either within yourself, on your team, o |
NewerOlder