Skip to content
The Chat Archive
gpt-3.5-turbo-0613· OpenAI WildChat-4.8M (AI2)

Подбори программных средства и/или административные мероприятий для минимазции рисков…

  1. User

    Подбори программных средства и/или административные мероприятий для минимазции рисков использования данной техники злоумышлениками и переведи на русский язык.

    Valid Accounts

    Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop.[1] Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

    In some cases, adversaries may abuse inactive accounts: for example, those belonging to individuals who are no longer part of an organization. Using these accounts may allow the adversary to evade detection, as the original account user will not be present to identify any anomalous activity taking place on their account.[2]

    The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.[3]

    ID: T1078 Sub-techniques: T1078.001, T1078.002, T1078.003, T1078.004 ⓘ Tactics: Defense Evasion, Persistence, Privilege Escalation, Initial Access ⓘ Platforms: Azure AD, Containers, Google Workspace, IaaS, Linux, Network, Office 365, SaaS, Windows, macOS ⓘ Permissions Required: Administrator, User ⓘ Effective Permissions: Administrator, User ⓘ Defense Bypassed: Anti-virus, Application Control, Firewall, Host Intrusion Prevention Systems, Network Intrusion Detection System, System Access Controls Contributors: Goldstein Menachem; Jon Sternstein, Stern Security; Mark Wee; Netskope; Praetorian; Prasad Somasamudram, McAfee; Sekhar Sarukkai, McAfee; Syed Ummar Farooqh, McAfee; Yossi Weizman, Azure Defender Research Team Version: 2.6 Created: 31 May 2017 Last Modified: 30 March 2023 Version Permalink Procedure Examples ID Name Description G0026 APT18 APT18 actors leverage legitimate credentials to log into external remote services.[4]

    G0007 APT28 APT28 has used legitimate credentials to gain initial access, maintain access, and exfiltrate data from a victim network. The group has specifically used credentials stolen through a spearphishing email to login to the DCCC network. The group has also leveraged default manufacturer's passwords to gain initial access to corporate networks via IoT devices such as a VOIP phone, printer, and video decoder.[5][6][7][8]

    G0016 APT29 APT29 has used a compromised account to access an organization's VPN infrastructure.[9]

    G0064 APT33 APT33 has used valid accounts for initial access and privilege escalation.[10][11]

    G0087 APT39 APT39 has used stolen credentials to compromise Outlook Web Access (OWA).[12]

    G0096 APT41 APT41 used compromised credentials to log on to other systems.[13][14]

    G0001 Axiom Axiom has used previously compromised administrative accounts to escalate privileges.[15]

    G0008 Carbanak Carbanak actors used legitimate credentials of banking employees to perform operations that sent them millions of dollars.[16]

    G0114 Chimera Chimera has used a valid account to maintain persistence via scheduled task.[17]

    G0035 Dragonfly Dragonfly has compromised user credentials and used valid accounts for operations.[18][19][20]

    S0567 Dtrack Dtrack used hard-coded credentials to gain access to a network share.[21]

    S0038 Duqu Adversaries can instruct Duqu to spread laterally by copying itself to shares it has enumerated and for which it has obtained legitimate credentials (via keylogging or other means). The remote host is then infected by using the compromised credentials to schedule a task on remote machines that executes the malware.[22]

    G0051 FIN10 FIN10 has used stolen credentials to connect remotely to victim networks using VPNs protected with only a single factor.[23]

    G0085 FIN4 FIN4 has used legitimate credentials to hijack email communications.[24][25]

    G0053 FIN5 FIN5 has used legitimate VPN, RDP, Citrix, or VNC credentials to maintain access to a victim environment.[26][27][28]

    G0037 FIN6 To move laterally on a victim network, FIN6 has used credentials stolen from various systems on which it gathered usernames and password hashes.[29][30][31]

    G0046 FIN7 FIN7 has harvested valid administrative credentials for lateral movement.[32]

    G0061 FIN8 FIN8 has used valid accounts for persistence and lateral movement.[33]

    G0117 Fox Kitten Fox Kitten has used valid credentials with various services during lateral movement.[34]

    G0093 GALLIUM GALLIUM leveraged valid accounts to maintain access to a victim network.[35]

    S0604 Industroyer Industroyer can use supplied user credentials to execute processes and stop services.[36]

    G0004 Ke3chang Ke3chang has used credential dumpers or stealers to obtain legitimate credentials, which they used to gain access to victim accounts.[37]

    S0599 Kinsing Kinsing has used valid SSH credentials to access remote hosts.[38]

    G1004 LAPSUSLAPSUS LAPSUS has used compromised credentials and/or session tokens to gain access into a victim's VPN, VDI, RDP, and IAMs.[39]

    G0032 Lazarus Group Lazarus Group has used administrator credentials to gain access to restricted network segments.[40]

    G0065 Leviathan Leviathan has obtained valid accounts to gain initial access.[41][42]

    S0362 Linux Rabbit Linux Rabbit acquires valid SSH accounts through brute force. [43]

    G0045 menuPass menuPass has used valid accounts including shared between Managed Service Providers and clients to move between the two environments.[44][45][46][47]

    C0002 Night Dragon During Night Dragon, threat actors used compromised VPN accounts to gain access to victim systems.[48]

    G0049 OilRig OilRig has used compromised credentials to access other systems on a victim network.[49][50][14]

    C0014 Operation Wocao During Operation Wocao, threat actors used valid VPN credentials to gain initial access.[51]

    G0011 PittyTiger PittyTiger attempts to obtain legitimate credentials during operations.[52]

    G1005 POLONIUM POLONIUM has used valid compromised credentials to gain access to victim environments.[53]

    G0034 Sandworm Team Sandworm Team have used previously acquired legitimate credentials prior to attacks.[54]

    S0053 SeaDuke Some SeaDuke samples have a module to extract email from Microsoft Exchange servers using compromised credentials.[55]

    G0091 Silence Silence has used compromised credentials to log on to other systems and escalate privileges.[56]

    G0122 Silent Librarian Silent Librarian has used compromised credentials to obtain unauthorized access to online accounts.[57]

    C0024 SolarWinds Compromise During the SolarWinds Compromise, APT29 used different compromised credentials for remote access and to move laterally.[58][59][60]

    G0039 Suckfly Suckfly used legitimate account credentials that they dumped to navigate the internal victim network as though they were the legitimate account owner.[61]

    G0088 TEMP.Veles TEMP.Veles has used compromised VPN accounts.[62]

    G0027 Threat Group-3390 Threat Group-3390 actors obtain legitimate credentials using a variety of methods and use them to further lateral movement on victim networks.[63]

    G0102 Wizard Spider Wizard Spider has used valid credentials for privileged accounts with the goal of accessing domain controllers.[64]

    Mitigations ID Mitigation Description M1036 Account Use Policies Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[65]

    M1015 Active Directory Configuration Disable legacy authentication, which does not support MFA, and require the use of modern authentication protocols instead.

    M1013 Application Developer Guidance Ensure that applications do not store sensitive data or credentials insecurely. (e.g. plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).

    M1027 Password Policies Applications and appliances that utilize default username and password should be changed immediately after the installation, and before deployment to a production environment.[66] When possible, applications that use SSH keys should be updated periodically and properly secured.

    Policies should minimize (if not eliminate) reuse of passwords between different user accounts, especially employees using the same credentials for personal accounts that may not be defended by enterprise security resources.

    M1026 Privileged Account Management Audit domain and local accounts as well as their permission levels routinely to look for situations that could allow an adversary to gain wide access by obtaining credentials of a privileged account. [3] [67] These audits should also include if default accounts have been enabled, or if new local accounts are created that have not be authorized. Follow best practices for design and administration of an enterprise network to limit privileged account use across administrative tiers. [68]

    M1018 User Account Management Regularly audit user accounts for activity and deactivate or remove any that are no longer needed.

    M1017 User Training Applications may send push notifications to verify a login as a form of multi-factor authentication (MFA). Train users to only accept valid push notifications and to report suspicious push notifications.

    Detection ID Data Source Data Component Detects DS0028 Logon Session Logon Session Creation Monitor for newly constructed logon behavior that may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Correlate other security systems with login information (e.g., a user has an active login session but has not entered the building or does not have VPN access).

    Logon Session Metadata Look for suspicious account behavior across systems that share accounts, either user, admin, or service accounts. Examples: one account logged into multiple systems simultaneously; multiple accounts logged into the same machine simultaneously; accounts logged in at odd times or outside of business hours. Activity may be from interactive login sessions or process ownership from accounts being used to execute binaries on a remote system as a particular account.

    DS0002 User Account User Account Authentication Monitor for an attempt by a user that may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.

  2. Assistant

    Минимизация рисков использования данной техники злоумышленниками может осуществляться путем применения следующих программных средств и административных мероприятий:

    1. Использование механизмов многофакторной аутентификации (MFA) для защиты учетных записей. Это позволит предотвратить несанкционированный доступ к учетным данным даже в случае компрометации пароля.

    2. Регулярное аудирование учетных записей пользователей и деактивация учетных записей, которые больше не используются. Это поможет устранить возможность злоумышленников использовать неактивные учетные записи для получения доступа в систему.

    3. Изменение паролей по умолчанию для приложений и устройств, которые используются в рабочей среде. Убедитесь, что пароли, используемые для доступа к учетным записям, длинные, сложные и уникальные.

    4. Ограничение привилегий пользователей и применение принципа минимальных привилегий. Убедитесь, что каждый пользователь имеет только необходимые привилегии для выполнения своих рабочих функций, чтобы ограничить возможность распространения атаки при компрометации учетной записи.

    5. Регулярное обучение пользователей основам кибербезопасности и информирование их о методах фишинга и других подобных атаках. Это поможет пользователям быть более бдительными и предотвратить компрометацию своих учетных данных.

    6. Реализация мониторинга активности учетных записей и обнаружение аномальной активности. Мониторинг логов входа в систему, а также распознавание необычного поведения учетных записей пользователей (например, одновременный вход в систему с нескольких устройств или вход в систему в нерабочее время) может помочь выявить компрометацию учетных данных.

    7. Продвижение использования паролей длинной и сложной, а также регулярное изменение паролей. Ресурсы для генерации и хранения уникальных паролей могут быть полезны для пользователей, чтобы избежать повторного использования паролей.

    8. Использование инструментов мониторинга сетевого трафика и обнаружение аномального сетевого поведения. Мониторинг трафика может помочь выявить необычные передачи данных или попытки несанкционированного доступа к ресурсам с использованием скомпрометированной учетной записи.

    9. Регулярное обновление программного обеспечения на серверах и рабочих станциях. Обновления содержат исправления уязвимостей, которые могут быть использованы злоумышленниками для компрометации учетных данных.

    10. Создание сегрегированных сетевых подсетей и ограничение доступа между ними. Это поможет предотвратить распространение атаки в случае компрометации одной учетной записи.

    Обратите внимание, что эти меры не гарантируют полной защиты от использования данной техники злоумышленниками, но они представляют собой важные шаги по минимизации рисков и реагированию на атаки.