[et_pb_section fb_built=”1″ _builder_version=”4.27.4″ _module_preset=”default” custom_padding=”||65px|||” global_colors_info=”{}”][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” locked=”off” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/nationalcybersecuritysociety.org\/wp-content\/uploads\/2025\/09\/NCSS-3397-Bulletin-Header-Footer-Header-Graphic-1600×350-Compressed.png” title_text=”NCSS-3397-Bulletin-Header-Footer-Header Graphic 1600×350-Compressed” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n
Published: December 12, 2025<\/em><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n Our new bulletin Cyber Threat Watch<\/em><\/strong> has been created to help small businesses stay up to date on the latest threats, news, and events affecting their business. The content has been curated to make cybersecurity easy and accessible for both technical and nontechnical readers.<\/span><\/p>\n [\/et_pb_text][et_pb_heading title=”Featured Cyber Incident \u2014 Amazon Web Services (AWS) Outage” _builder_version=”4.27.4″ _module_preset=”default” title_level=”h2″ title_font=”|600|||||||” title_text_color=”#00688E” global_colors_info=”{}”][\/et_pb_heading][et_pb_image src=”https:\/\/nationalcybersecuritysociety.org\/wp-content\/uploads\/2025\/12\/AdobeStock_733206738_Editorial_Use_Only.jpg” title_text=”AdobeStock_733206738_Editorial_Use_Only” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” header_3_text_color=”#00688E” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n On October 20, 2025, a major service disruption at Amazon Web Services (AWS) caused widespread interruptions to cloud-based services used by organizations worldwide<\/a>. Although AWS restored essential functions within hours, the outage showed how a single issue can quickly disrupt the cloud services many businesses rely on.<\/span><\/p>\n For small businesses using online applications, it served as a reminder that unexpected disruptions can come from outside their own systems. This reinforces why your business needs a simple incident response plan\u2014with clear crisis communication steps\u2014to maintain resilience and stakeholder trust when a third-party service goes down.<\/p>\n The outage began when an automated process for a core service in the US-East-1 region inside AWS systems mistakenly removed a Domain Name System (DNS)<\/a> record, a directory that helps systems find the correct online location for a service. Without this record, the systems could no longer look up where to connect, and AWS tools that depend on it began to fail. Consequently, background functions used for logging in and processing requests slowed down or went offline. These problems then spread outward to external business tools\u2014such as payment systems, booking platforms, and document-sharing tools\u2014that rely on AWS. <\/span><\/p>\n After AWS identified the cause and restored the DNS record, most services gradually recovered as backlogs cleared within the day. However, this incident showed how one small error from a third-party provider can ripple outward and interrupt business operations.<\/span><\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/nationalcybersecuritysociety.org\/wp-content\/uploads\/2025\/12\/AdobeStock_1087548181.jpg” title_text=”AdobeStock_1087548181″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” header_3_text_color=”#00688E” custom_css_free_form=”ol {|| list-style: none !important; || counter-reset: item; ||}||||ol li {|| counter-increment: item; || position: relative; || padding-left: 2em; \/* Adjust as needed for spacing *\/||}||||ol li::before {|| content: counter(item) %22.%22; || font-weight: bold; || position: absolute;|| left: 0; || width: 1.5em; || text-align: right;||}” global_colors_info=”{}”]<\/p>\n One factor that helped prevent the outage from escalating further was AWS\u2019s structured incident response and continuous communication. The company activated engineering teams, diagnosed the issue, stabilized the system, and kept its public status pages updated throughout the morning of the incident. After recovery, AWS published a clear summary explaining the cause and future safeguards<\/a>. This approach reduced confusion and helped other organizations understand the impact.<\/span><\/p>\n Small businesses can apply the same principles, even without technical expertise. An incident response plan is not only about fixing a problem\u2014it also guides how a business communicates with customers, vendors, and partners who may rely on its services. When systems slow down or become unavailable, early and accurate communication helps maintain trust, reduce users\u2019 frustration, and protect important business relationships. A simple plan ensures that staff know who communicates what, when, and through which channels.<\/span><\/p>\n The following steps help your business stay organized and responsive when a third-party outage affects your operations.<\/span><\/p>\n The AWS disruption highlighted how dependent many organizations are on external services. Simple preparation and clear communication can help your business manage unexpected interruptions and protect stakeholder confidence.<\/p>\n The NCSS encourages businesses to adopt comprehensive security practices and stay informed about evolving threats. We recommend you consider becoming an NCSS member to access a wide range of our services. For more information, visit our Small Business page<\/a><\/span>.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”|auto|-44px|auto||” custom_padding=”71px||0px|||” locked=”off” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”||-2px|||” locked=”off” global_colors_info=”{}”][\/et_pb_divider][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” header_2_font=”|600|||||||” header_2_text_color=”#00688E” custom_margin=”||2px|||” custom_padding=”||0px|||” global_colors_info=”{}”]<\/p>\n https:\/\/aws.amazon.com\/message\/101925\/<\/a> <\/span><\/p>\n https:\/\/www.cnn.com\/2025\/10\/20\/tech\/aws-why-internet-outages-keep-happening<\/a><\/span><\/p>\n https:\/\/www.cnn.com\/business\/live-news\/amazon-tech-outage-10-20-25-intl<\/a><\/span><\/p>\n https:\/\/www.theguardian.com\/technology\/2025\/oct\/24\/amazon-reveals-cause-of-aws-outage<\/a><\/span><\/p>\n https:\/\/www.axiapr.com\/blog\/what-the-aws-outage-teaches-every-brand-about-crisis-communication<\/a><\/span><\/p>\nHow the Incident Unfolded<\/h3>\n
Why It Matters to Your Business<\/h3>\n
How Your Business Can Be Prepared<\/h3>\n
\n
Conclusion<\/span><\/h3>\n
References<\/h2>\n