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
My idea would be to provide common assets (like MS Office, Windows XY, ...) that can be found in almost every organization as specializations of the core assets (with common attack steps already implemented). I think that customers would appreciate to have their well known assets already around without sticking them together.
coreLang is now very general and expressive. We do however have to be able to express specific systems, like a RHEL 8.0 or a Windows 2008R2 server.
They are similar in some respects, but different in other and they seem to be more or less secure relative to each other.
We need to be clear on how to represent e.g. a more vulnerable Windows 2008R2 system compared to a Less vulnerable RHEL 8.0.
Approaches may be different TTC functions on specialized assets (not very flexible), or use of some kind of vulnerability associations.
Components may very well play an important role in how to represent this.
Components
The text was updated successfully, but these errors were encountered: