You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if it makes sense to have a danger tag that causes am-i-isolated to simulate real attack scenarios. For example, attempts to read from /proc/1/environ, access /proc/sysrq-trigger, mount the host filesystem inside the container, read kernel modules, etc. This gives a real-world simulation about the risks present in their environment, without being destructive (hence the simulation)
The text was updated successfully, but these errors were encountered:
I wonder if it makes sense to have a danger tag that causes am-i-isolated to simulate real attack scenarios. For example, attempts to read from
/proc/1/environ
, access/proc/sysrq-trigger
, mount the host filesystem inside the container, read kernel modules, etc. This gives a real-world simulation about the risks present in their environment, without being destructive (hence the simulation)The text was updated successfully, but these errors were encountered: