Forum Discussion
Attack Simulator Email problem
Hi, Im having some problems with the Attack Simulator. I work for a mid-sized company roughly ~900 staff. We have run attack simulations in the past with a credential harvest payload, but...
If you use automation and the randomization feature to drop your payload then it is supposed to drop attacks of over 1,000 in batches of 1,000 and attacks of less than 1,000 in batches of 100, BUT (1) that was the Support position over a year ago and the attack simulator has changed significantly since then, (2) I have not used automation since that time, and (3) I cannot remember how well this worked. I do remember that within a batch, all mails are delivered in quick succession so you still get the "water cooler" effect the designers were trying to avoid. I also have the impression that automation and randomization would work better with a large bundle of payloads rather than just the one, so over a period of several months your recipients would see the payloads in any order.
If your 900 are geographically scattered then try slicing your user base by name and then attack those in small groups. It is a bit more work but PowerShell can write the attack lists for you fairly quickly then they go straight into the attack simulator. You can mix payrolls manually that way if you wish.
If your 900 are geographically scattered then try slicing your user base by name and then attack those in small groups. It is a bit more work but PowerShell can write the attack lists for you fairly quickly then they go straight into the attack simulator. You can mix payrolls manually that way if you wish.