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
During the integration of metta with my simulation platform I noticed that there are several metta config files that have the incorrect mitre_attack_technique mapping to the actual MITRE technique name. Perhaps MITRE made small changes to their model :) It involves the following differences (ie. wrong mitre_attack_technique vs correct mitre names):
mitre_attack_technique: System Owner-User Discovery mitre: System Owner/User Discovery
mitre_attack_technique: Registry Run Keys / Start Folder mitre: Registry Run Keys / Startup Folder
mitre_attack_technique: Lateral Movement with SSH Agent Hijacking mitre: SSH Hijacking
During the integration of metta with my simulation platform I noticed that there are several metta config files that have the incorrect mitre_attack_technique mapping to the actual MITRE technique name. Perhaps MITRE made small changes to their model :) It involves the following differences (ie. wrong mitre_attack_technique vs correct mitre names):
mitre_attack_technique: System Owner-User Discovery
mitre: System Owner/User Discovery
mitre_attack_technique: Registry Run Keys / Start Folder
mitre: Registry Run Keys / Startup Folder
mitre_attack_technique: Lateral Movement with SSH Agent Hijacking
mitre: SSH Hijacking
mitre_attack_technique: Powershell
mitre: PowerShell
mitre_attack_technique: Cron Job
mitre: Local Job Scheduling
The text was updated successfully, but these errors were encountered: