-
https://threats.wiz.io/all-incidents
-
Threats CC.AuC.DFrXSS.3, CC.AuC.DFsXSS.3, CC.AuC.DSrXSS.3 and CC.AuC.DSsXSS.3 represent stored or reflected XSS attacks on the client or server side. They assume that the goal of the attacker will be …
-
Currently, restic threat model assumes that host which is being backed up is fully trusted; that assumption is reasonable. For certain backends, there is a support for an _append only_ mode, which hel…
-
Because of the way TACS spawns raids and the way dark entities are handled, it throws an error and fails to spawn the 'raid'
![image](https://github.com/Dubwise56/Rimatomics/assets/61633596/bce50f91-…
-
When defining sumologic_monitor entities even if the sumologic_folder resource is in the same state, the monitor will fail creation if the parent_id is set to a sumologic_folder:
parent_id= sumolog…
-
Hey.
I just tested this bot but it doesn't seem to recognize any threats.
I posted a few links directly from Phishing.Database's lists (old ones, new ones, doesn't matter), the bot marked all of t…
-
So, the threats on layer 8 are less mechanically driven than the threats on previous layers, so I'm not sure the best way to implement them.
For the inanis ego, I was thinking a series of events w…
-
Threats DF.O.CCDFSFC.3 and DF.O.CCDFSTC.3 model potential attacks on a service by a client that normally sends data to or receives data from the service. The threats model the possibility that a malic…
-
Describe what problem your feature request solves:
Currently the tool does a good job for decomposing the architecture and applying threats according to the STRIDE framework. This still leaves some g…
-
In the past, it was necessary for every primary or secondary threat to have at least one role-level cause, i.e., a cause defined in terms of an asset behaviour (for secondary threats) or TWA (for prim…