id
int64 1
14.4k
| text
stringlengths 3
5.01k
| entities
list | relations
list | Comments
list |
|---|---|---|---|---|
713 | Please mark, I'm not a robot! | [] | [] | [] |
714 | By submitting this form, you agree to our Terms of Use and acknowledge our Privacy Statement. | [] | [] | [] |
715 | This post is also available in: 日本語 (Japanese) On Aug. 25, 2021, Atlassian released a security advisory for an injection vulnerability in Confluence Server and Data Center, CVE-2021-26084. | [
{
"id": 46281,
"label": "vulnerability",
"start_offset": 179,
"end_offset": 193
},
{
"id": 46282,
"label": "SOFTWARE",
"start_offset": 144,
"end_offset": 177
},
{
"id": 46279,
"label": "identity",
"start_offset": 71,
"end_offset": 80
},
{
"id": 46280,
"label": "TIME",
"start_offset": 56,
"end_offset": 69
}
] | [
{
"id": 178,
"from_id": 46282,
"to_id": 46281,
"type": "has"
}
] | [] |
716 | If the vulnerability is exploited, threat actors could bypass authentication and run arbitrary code on unpatched systems. | [
{
"id": 46283,
"label": "attack-pattern",
"start_offset": 55,
"end_offset": 76
},
{
"id": 46284,
"label": "attack-pattern",
"start_offset": 81,
"end_offset": 99
}
] | [] | [] |
717 | Since the release of this advisory, mass scanning activity has started to occur, seeking unpatched systems, and in-the-wild exploitation has begun. | [] | [] | [] |
718 | Unit 42 recommends customers upgrade to the latest release of Confluence Server and Data Center. | [
{
"id": 46285,
"label": "identity",
"start_offset": 0,
"end_offset": 7
},
{
"id": 46286,
"label": "SOFTWARE",
"start_offset": 62,
"end_offset": 95
}
] | [] | [] |
719 | The Atlassian products vulnerable to CVE-2021-26084 are those using the following versions of Confluence Server and Data Center: Confluence Cloud customers are not affected by this vulnerability. | [
{
"id": 46287,
"label": "identity",
"start_offset": 5,
"end_offset": 14
},
{
"id": 46288,
"label": "vulnerability",
"start_offset": 38,
"end_offset": 52
},
{
"id": 46290,
"label": "SOFTWARE",
"start_offset": 131,
"end_offset": 147
},
{
"id": 46289,
"label": "SOFTWARE",
"start_offset": 95,
"end_offset": 128
}
] | [
{
"id": 180,
"from_id": 46289,
"to_id": 46288,
"type": "has"
}
] | [] |
720 | We recommend that customers update Atlassian Confluence Server and Data Center to the latest version, 7.13.0 (TLS). | [
{
"id": 44838,
"label": "SOFTWARE",
"start_offset": 36,
"end_offset": 79
}
] | [] | [] |
721 | You can find the newest release on Atlassian’s download center. | [
{
"id": 46291,
"label": "identity",
"start_offset": 35,
"end_offset": 44
}
] | [] | [] |
722 | If you cannot install the latest upgrade, see the Mitigation section on the Atlassian security advisory for information on how to mitigate this vulnerability by running a script for the operating system your Confluence server is hosted on. Palo Alto Networks provides protection against the exploitation of this vulnerability: Palo Alto Networks will update this Threat Brief with new information and recommendations as they become available. | [
{
"id": 46292,
"label": "identity",
"start_offset": 77,
"end_offset": 86
},
{
"id": 46293,
"label": "SOFTWARE",
"start_offset": 209,
"end_offset": 219
},
{
"id": 46294,
"label": "identity",
"start_offset": 242,
"end_offset": 260
},
{
"id": 46295,
"label": "identity",
"start_offset": 330,
"end_offset": 348
}
] | [] | [] |
723 | writeups/Confluence-RCE.md at main · httpvoid/writeups Confluence Server Download Archives Confluence Security Advisory - 2021-08-25 | Confluence Data Center and Server 7.13 | [
{
"id": 46296,
"label": "TIME",
"start_offset": 125,
"end_offset": 135
},
{
"id": 46297,
"label": "SOFTWARE",
"start_offset": 138,
"end_offset": 177
},
{
"id": 44839,
"label": "FILEPATH",
"start_offset": 1,
"end_offset": 27
},
{
"id": 44841,
"label": "SOFTWARE",
"start_offset": 57,
"end_offset": 74
},
{
"id": 44842,
"label": "SOFTWARE",
"start_offset": 94,
"end_offset": 104
}
] | [] | [] |
724 | Sign up to receive the latest news, cyber threat intelligence and research from us Please enter your email address! | [] | [] | [] |
725 | Please mark, I'm not a robot! By submitting this form, you agree to our Terms of Use and acknowledge our Privacy Statement. | [] | [] | [] |
726 | This post is also available in: 日本語 (Japanese) On Sept. 14, 2021, Microsoft’s Security Response Center (MSRC) released security patches detailing the findings of four critical vulnerabilities affecting the Microsoft Azure package Open Management Infrastructure (OMI). | [
{
"id": 46298,
"label": "TIME",
"start_offset": 56,
"end_offset": 70
},
{
"id": 44843,
"label": "identity",
"start_offset": 72,
"end_offset": 115
},
{
"id": 44844,
"label": "SOFTWARE",
"start_offset": 212,
"end_offset": 272
}
] | [] | [] |
727 | The open-source OMI package is designed to provide a portable infrastructure backbone for web-based management tools, such as diagnostic monitoring, log analytic services and automation functionality within UNIX and Linux systems. | [
{
"id": 46299,
"label": "SOFTWARE",
"start_offset": 207,
"end_offset": 211
},
{
"id": 46301,
"label": "SOFTWARE",
"start_offset": 16,
"end_offset": 27
},
{
"id": 46300,
"label": "SOFTWARE",
"start_offset": 216,
"end_offset": 221
}
] | [] | [] |
728 | OMI is used by Microsoft Azure to manage UNIX packages within Azure virtual machines (VMs), containers and serverless cloud instances. | [
{
"id": 46302,
"label": "SOFTWARE",
"start_offset": 0,
"end_offset": 3
},
{
"id": 46305,
"label": "SOFTWARE",
"start_offset": 62,
"end_offset": 90
},
{
"id": 46303,
"label": "SOFTWARE",
"start_offset": 15,
"end_offset": 30
},
{
"id": 46304,
"label": "SOFTWARE",
"start_offset": 41,
"end_offset": 45
}
] | [] | [] |
729 | According to Microsoft’s security release notes, any system created, or which has updated its OMI package, after Aug. 11, 2021, should automatically be patched. | [
{
"id": 44845,
"label": "TIME",
"start_offset": 113,
"end_offset": 126
},
{
"id": 44846,
"label": "identity",
"start_offset": 13,
"end_offset": 23
}
] | [] | [] |
730 | The four critical vulnerabilities discovered by security researchers from Wiz include one unauthenticated remote code execution (RCE) and three privilege escalation vulnerabilities. Dubbed OMIGOD, the four vulnerabilities were found to directly affect Azure cloud instances using the following Azure services: Prisma Cloud Compute Defender agents can detect whether any Azure system is vulnerable to any of the four CVEs. | [
{
"id": 46306,
"label": "attack-pattern",
"start_offset": 91,
"end_offset": 135
},
{
"id": 46311,
"label": "SOFTWARE",
"start_offset": 313,
"end_offset": 342
},
{
"id": 46307,
"label": "attack-pattern",
"start_offset": 145,
"end_offset": 165
},
{
"id": 46309,
"label": "SOFTWARE",
"start_offset": 254,
"end_offset": 265
},
{
"id": 46310,
"label": "SOFTWARE",
"start_offset": 296,
"end_offset": 310
},
{
"id": 46313,
"label": "SOFTWARE",
"start_offset": 373,
"end_offset": 378
},
{
"id": 46308,
"label": "vulnerability",
"start_offset": 191,
"end_offset": 197
}
] | [] | [] |
731 | Additionally, Prisma Cloud users can also build a custom vulnerability detection rule to identify if any system is running an OMI package with a version previous to 1.6.8.1. | [
{
"id": 46314,
"label": "SOFTWARE",
"start_offset": 14,
"end_offset": 26
},
{
"id": 46315,
"label": "SOFTWARE",
"start_offset": 126,
"end_offset": 129
}
] | [] | [] |
732 | To build a custom vulnerability detection rule, open Prisma Cloud and navigate to the following page: name,type,package,minVersionInclusive,maxVersionInclusive,md5 OMIGOD,package,omi,*,1.6.8.0, Palo Alto Networks Azure-based VM- and CN-Series Firewall instances do not use the OMI package and are not vulnerable to the OMI critical vulnerabilities. | [
{
"id": 46318,
"label": "identity",
"start_offset": 197,
"end_offset": 215
},
{
"id": 46319,
"label": "SOFTWARE",
"start_offset": 216,
"end_offset": 221
},
{
"id": 46321,
"label": "SOFTWARE",
"start_offset": 322,
"end_offset": 325
},
{
"id": 46317,
"label": "vulnerability",
"start_offset": 166,
"end_offset": 172
},
{
"id": 46316,
"label": "SOFTWARE",
"start_offset": 54,
"end_offset": 66
},
{
"id": 46320,
"label": "SOFTWARE",
"start_offset": 280,
"end_offset": 283
}
] | [] | [] |
733 | Prisma Cloud will create an alert for any system which maintains an OMI package vulnerable to the OMI critical vulnerabilities. | [
{
"id": 46322,
"label": "SOFTWARE",
"start_offset": 1,
"end_offset": 13
},
{
"id": 46324,
"label": "SOFTWARE",
"start_offset": 99,
"end_offset": 102
},
{
"id": 46323,
"label": "SOFTWARE",
"start_offset": 69,
"end_offset": 73
}
] | [] | [] |
734 | Should a system be identified as vulnerable, the following steps should be taken for that Azure Cloud Instance: | [
{
"id": 46325,
"label": "SOFTWARE",
"start_offset": 90,
"end_offset": 101
}
] | [] | [] |
735 | On Sept. 14, 2021, security researchers from Wiz released a report detailing the findings of four critical vulnerabilities affecting the Microsoft Azure package OMI. | [
{
"id": 46326,
"label": "identity",
"start_offset": 45,
"end_offset": 48
},
{
"id": 44849,
"label": "TIME",
"start_offset": 3,
"end_offset": 17
},
{
"id": 44851,
"label": "SOFTWARE",
"start_offset": 137,
"end_offset": 164
}
] | [] | [] |
736 | Dubbed OMIGOD, the four vulnerabilities were found to directly affect Azure Cloud Instances. | [
{
"id": 46327,
"label": "vulnerability",
"start_offset": 7,
"end_offset": 13
},
{
"id": 46328,
"label": "SOFTWARE",
"start_offset": 70,
"end_offset": 81
}
] | [
{
"id": 181,
"from_id": 46328,
"to_id": 46327,
"type": "has"
}
] | [] |
737 | Palo Alto Networks Azure-based VM and CN Series Firewall instances do not use the OMI package and are not vulnerable to the OMI critical vulnerabilities. | [
{
"id": 46331,
"label": "SOFTWARE",
"start_offset": 82,
"end_offset": 85
},
{
"id": 46330,
"label": "SOFTWARE",
"start_offset": 19,
"end_offset": 24
},
{
"id": 46329,
"label": "identity",
"start_offset": 0,
"end_offset": 18
},
{
"id": 46332,
"label": "SOFTWARE",
"start_offset": 124,
"end_offset": 127
}
] | [] | [] |
738 | Customers of Prisma Cloud have the ability to create alerts to detect vulnerabilities. | [
{
"id": 44852,
"label": "SOFTWARE",
"start_offset": 13,
"end_offset": 25
}
] | [] | [] |
739 | Sign up to receive the latest news, cyber threat intelligence and research from us Please enter your email address! | [] | [] | [] |
740 | Please mark, I'm not a robot! By submitting this form, you agree to our Terms of Use and acknowledge our Privacy Statement. | [] | [] | [] |
741 | Use-after-free bugs have affected Internet Explorer for years. | [
{
"id": 46333,
"label": "SOFTWARE",
"start_offset": 34,
"end_offset": 51
}
] | [] | [] |
742 | In the past year alone, Microsoft patched 122 IE vulnerabilities, the majority of which were use-after-free bugs. | [
{
"id": 46334,
"label": "identity",
"start_offset": 24,
"end_offset": 33
}
] | [] | [] |
743 | This year Microsoft has already patched 126 IE vulnerabilities to date. | [
{
"id": 46335,
"label": "identity",
"start_offset": 10,
"end_offset": 19
}
] | [] | [] |
744 | Of those vulnerabilities, 4 were actively being exploited in the wild. | [] | [] | [] |
745 | These 4 exploits (CVE-2014-1815, CVE-2014-1776, CVE-2014-0322, CVE-2014-0324) were all based on use-after-free bugs. | [
{
"id": 46336,
"label": "vulnerability",
"start_offset": 18,
"end_offset": 31
},
{
"id": 46337,
"label": "vulnerability",
"start_offset": 33,
"end_offset": 46
},
{
"id": 46339,
"label": "vulnerability",
"start_offset": 63,
"end_offset": 76
},
{
"id": 46338,
"label": "vulnerability",
"start_offset": 48,
"end_offset": 61
}
] | [] | [] |
746 | To deal with the increasing number of use-after-free bugs and associated exploits, Microsoft introduced a series of new control mechanisms in the most recent Internet Explorer patches. | [
{
"id": 46340,
"label": "identity",
"start_offset": 84,
"end_offset": 93
},
{
"id": 46341,
"label": "SOFTWARE",
"start_offset": 159,
"end_offset": 176
}
] | [] | [] |
747 | In June, Microsoft introduced a new isolated heap mechanism to solve the usage issue of use-after-free exploitation. | [
{
"id": 44853,
"label": "identity",
"start_offset": 9,
"end_offset": 18
},
{
"id": 44854,
"label": "attack-pattern",
"start_offset": 88,
"end_offset": 115
}
] | [] | [] |
748 | They followed that up In July by implementing a deferred free method to solve the freeing issue of use-after-free bugs. | [
{
"id": 46342,
"label": "TIME",
"start_offset": 25,
"end_offset": 29
},
{
"id": 46343,
"label": "attack-pattern",
"start_offset": 99,
"end_offset": 113
}
] | [] | [] |
749 | The main concept of an isolated heap is simple. | [] | [] | [] |
750 | It allocates a dedicated heap for select critical objects to use that is separate from other heaps that a user can directly access. | [] | [] | [] |
751 | The heap block will not be occupied by user-controlled data after the critical objects are freed. | [] | [] | [] |
752 | This mechanism prevents precise control of the data of a freed object from further exploitation. | [] | [] | [] |
753 | Figure 1. _g_hIsolatedHeap handle used for isolated heap | [] | [] | [] |
754 | The isolated heap was applied to many but not all internal objects, leaving some still vulnerable. | [] | [] | [] |
755 | To address this, Microsoft introduced another protection method of deferred free named ProtectedFree. | [
{
"id": 46344,
"label": "identity",
"start_offset": 17,
"end_offset": 26
}
] | [] | [] |
756 | They encapsulate this method and apply it to almost every object in mshtml.dll. | [
{
"id": 44855,
"label": "FILEPATH",
"start_offset": 68,
"end_offset": 78
}
] | [] | [] |
757 | In IE9, for example, it has been applied to every object through MemoryProtection::HeapFree as shown in figure 2. | [
{
"id": 46345,
"label": "SOFTWARE",
"start_offset": 3,
"end_offset": 6
}
] | [] | [] |
758 | Figure 2. | [] | [] | [] |
759 | References of MemoryProtection::HeapFree | [] | [] | [] |
760 | The main idea of this protection mechanism is to delay the freeing action so that the intruder is unable to determine when they can occupy the freed object using controlled data. | [] | [] | [] |
761 | In this new patch, every time Internet Explorer tries to free an object, it is not freed immediately. | [
{
"id": 46346,
"label": "SOFTWARE",
"start_offset": 30,
"end_offset": 47
}
] | [] | [] |
762 | Instead, the block to be freed is marked and filled with 0x00 data and added to a pool. | [] | [] | [] |
763 | When the size of the pool hits a predefined threshold, which is currently 100k (0x186A0 as highlighted in figure 3), it performs the real freeing operation (ReclaimUnmarkedBlocks). Figure 3. | [] | [] | [] |
764 | C++ style pseudo code of ProtectedFree function | [] | [] | [] |
765 | Microsoft stores the to-be-freed blocks in a structure called st_ProtecFreeManageHeap. | [
{
"id": 44856,
"label": "identity",
"start_offset": 0,
"end_offset": 9
}
] | [] | [] |
766 | This structure is created in the function MemoryProtection::CMemoryProtector::ProtectCurrentThread and is used to manage deferred free heap blocks. | [] | [] | [] |
767 | Figure 4 shows an example of the structure in memory. | [] | [] | [] |
768 | Figure 4. st_ProtecFreeManageHeap Figure 5 provides an alternate view of the structure in a C style code block. | [] | [] | [] |
769 | Figure 5. C style code of st_ProtecFreeManageHeap | [] | [] | [] |
770 | If we were able to make the size of the current heap block in this structure larger than the threshold of 0x186A0 bytes and trigger CMemoryProtector::ProtectedFree, it is still possible to force a true freeing action and occupy the freed object with other data as we show in the following piece of javascript code in figure 6. Figure 6. Javascript proof of concept to force freeing When creating the anchor element, the debug logs are shown in figure 7. | [
{
"id": 46347,
"label": "SOFTWARE",
"start_offset": 340,
"end_offset": 350
}
] | [] | [] |
771 | The address of the anchor element is 0x0c3b3f98. | [] | [] | [] |
772 | Figure 7: | [] | [] | [] |
773 | Before free We then manually decrease the reference number, so the CMemoryProtector::ProtectedFree function will fill the block with 0’s, but the object is still not freed. | [] | [] | [] |
774 | Figure 8: decrease the reference number, not yet freed | [] | [] | [] |
775 | Finally we make the size of the CMemoryProtector::ProtectedFree management structure larger than 0x186a0 forcing the freeing operation. | [] | [] | [] |
776 | Figure 9: field “TotalMemorySize” of st_ProtecFreeManageHeap is greater than threshold | [] | [] | [] |
777 | The anchor element is now actually freed as shown in figure 10. | [] | [] | [] |
778 | Figure 10: object is in the free list now | [] | [] | [] |
779 | From a researchers' point of view, deferred free created a few problems, one of the major ones being that the page heap feature may not work correctly. | [] | [] | [] |
780 | Page heap is a useful feature for debugging. | [] | [] | [] |
781 | When page heap is turned on, the system allows only one object in one memory page. | [] | [] | [] |
782 | Once this object is freed the whole page is marked as invalid. | [] | [] | [] |
783 | So the next time IE tries to access a freed object an invalid address exception would be raised. | [
{
"id": 46348,
"label": "SOFTWARE",
"start_offset": 17,
"end_offset": 20
}
] | [] | [] |
784 | This mechanism is extremely helpful when researchers are trying to find use-after-free bugs. | [] | [] | [] |
785 | With the introduction of the deferred free patch the object is no longer truly freed, so the page still exists. | [] | [] | [] |
786 | In this situation the researcher is no longer able to determine whether a use-after-free behavior has occurred because no exception would be thrown out. | [] | [] | [] |
787 | To reduce the impact of the deferred free patch, a research may consider patching the mshtml.dll in memory. | [
{
"id": 46349,
"label": "FILEPATH",
"start_offset": 86,
"end_offset": 96
}
] | [] | [] |
788 | For example, you can call MemoryProtection::CMemoryProtector::UnprotectProcess before you perform any fuzzing tasks. | [
{
"id": 46350,
"label": "attack-pattern",
"start_offset": 102,
"end_offset": 109
}
] | [] | [] |
789 | The recent patches and introduction of isolated heap and deferred free are strong signs that Microsoft plans to address the fundamentals of use-after-free exploitation in a preventative manner rather than to passively patch the vulnerabilities as they are discovered. | [
{
"id": 44857,
"label": "identity",
"start_offset": 94,
"end_offset": 103
},
{
"id": 44858,
"label": "attack-pattern",
"start_offset": 141,
"end_offset": 168
}
] | [] | [] |
790 | From the results of our research, applications of such methods can effectively stop unpatched use-after-free attacks. | [
{
"id": 46351,
"label": "attack-pattern",
"start_offset": 94,
"end_offset": 116
}
] | [] | [] |
791 | It can also make the exploitations of heap overflows or type confusion bugs significantly more difficult. | [
{
"id": 46353,
"label": "attack-pattern",
"start_offset": 21,
"end_offset": 52
}
] | [] | [] |
792 | But this is not the end. | [] | [] | [] |
793 | For the foreseeable future, Microsoft may introduce more defensive mechanisms against use-after-free bugs or even heap fengshui to reduce the risk of being exploited. | [
{
"id": 46354,
"label": "identity",
"start_offset": 29,
"end_offset": 38
}
] | [] | [] |
794 | Could it be game over for use-after-free exploitation, or it is just the beginning of another cat and mouse game? | [] | [] | [] |
795 | Time will tell. | [] | [] | [] |
796 | Sign up to receive the latest news, cyber threat intelligence and research from us Please enter your email address! | [] | [] | [] |
797 | Please mark, I'm not a robot! | [] | [] | [] |
798 | By submitting this form, you agree to our Terms of Use and acknowledge our Privacy Statement. | [] | [] | [] |
799 | Today we’re releasing a new Unit 42 white paper titled “Credential-Based Attacks: Exposing the Ecosystem and Motives Behind Credential Phishing, Theft and Abuse.” | [
{
"id": 2601,
"label": "identity",
"start_offset": 28,
"end_offset": 35
},
{
"id": 2604,
"label": "attack-pattern",
"start_offset": 135,
"end_offset": 143
}
] | [] | [] |
800 | In this paper, we look at the problem of credential theft by exploring how it happens, what attackers do with credentials once they’ve stolen them, and what you can do to help prevent credential-based attacks. | [
{
"id": 46355,
"label": "attack-pattern",
"start_offset": 184,
"end_offset": 208
}
] | [] | [] |
801 | Credentials and authentication have become synonymous, with valid credentials allowing access to sensitive resources. | [] | [] | [] |
802 | Adversaries are increasingly stealing and using credentials as part of their playbooks; impersonating legitimate users to access a company’s most sensitive information, erase data on servers, and reconfigure them so that they can’t boot; and undertake other malicious activities. | [] | [] | [] |
803 | Stolen credentials underpin some of the most critical and damaging attacks out there; both Shamoon 2 and the Sofacy threat actor group, for example, have made detailed use of credential theft. | [
{
"id": 46358,
"label": "attack-pattern",
"start_offset": 175,
"end_offset": 191
},
{
"id": 46356,
"label": "threat-actor",
"start_offset": 109,
"end_offset": 134
},
{
"id": 46357,
"label": "threat-actor",
"start_offset": 91,
"end_offset": 100
}
] | [
{
"id": 182,
"from_id": 46357,
"to_id": 46358,
"type": "uses"
},
{
"id": 183,
"from_id": 46356,
"to_id": 46358,
"type": "uses"
}
] | [] |
804 | Credential theft today can happen in many ways, but the most notable are through credential phishing and the use of malware like keyloggers (both staples of the Sofacy group), as well as password reuse. | [
{
"id": 44859,
"label": "attack-pattern",
"start_offset": 1,
"end_offset": 17
},
{
"id": 44860,
"label": "attack-pattern",
"start_offset": 82,
"end_offset": 101
},
{
"id": 44861,
"label": "attack-pattern",
"start_offset": 130,
"end_offset": 140
},
{
"id": 44862,
"label": "threat-actor",
"start_offset": 162,
"end_offset": 174
},
{
"id": 44863,
"label": "attack-pattern",
"start_offset": 188,
"end_offset": 202
}
] | [
{
"id": 33,
"from_id": 44862,
"to_id": 44863,
"type": "uses"
},
{
"id": 34,
"from_id": 44862,
"to_id": 44861,
"type": "uses"
},
{
"id": 35,
"from_id": 44862,
"to_id": 44860,
"type": "uses"
},
{
"id": 36,
"from_id": 44862,
"to_id": 44859,
"type": "uses"
}
] | [] |
805 | The impact of a successful credential theft is, ultimately, access and authorization. | [
{
"id": 46359,
"label": "attack-pattern",
"start_offset": 27,
"end_offset": 43
}
] | [] | [] |
806 | Attackers will use credential theft for remote access to an organization, to access cloud-based resources (which may have weaker credential protections than network-based resources), or to move laterally within an organization once they’ve gained entry. | [
{
"id": 46360,
"label": "attack-pattern",
"start_offset": 19,
"end_offset": 35
}
] | [] | [] |
807 | The most sophisticated attacks can – and do – blend these actions together, sometimes using multiple stolen credentials to penetrate networks, move laterally within them, elevate privileges, and then access and steal data. Prevention of credential theft is too often overlooked. | [
{
"id": 46361,
"label": "attack-pattern",
"start_offset": 238,
"end_offset": 254
},
{
"id": 44864,
"label": "attack-pattern",
"start_offset": 101,
"end_offset": 119
},
{
"id": 44865,
"label": "attack-pattern",
"start_offset": 143,
"end_offset": 157
},
{
"id": 44866,
"label": "attack-pattern",
"start_offset": 171,
"end_offset": 188
},
{
"id": 44867,
"label": "attack-pattern",
"start_offset": 200,
"end_offset": 221
}
] | [] | [] |
808 | Organizations should continue with user education to help users better spot and not fall for phishing and spam attacks. | [
{
"id": 46362,
"label": "attack-pattern",
"start_offset": 93,
"end_offset": 118
}
] | [] | [] |
809 | You and your employees can also use password managers to make unique, complex passwords for each site not just a goal but a reality. | [] | [] | [] |
810 | Technology is also catching up; recent advances in two-factor/multi-factor authentication (2FA/MFA) and one-time passwords (OTP) represent the best long-term approaches to preventing credential theft. | [
{
"id": 46363,
"label": "attack-pattern",
"start_offset": 183,
"end_offset": 199
}
] | [] | [] |
811 | (Our newest release, PAN-OS 8.0, also includes protections to significantly limit or eliminate password reuse.) | [] | [] | [] |
812 | Get your copy of our white paper here. | [] | [] | [] |