- Published
- Source
- AWS Security Blog
- Filed under
- Cloud, Identity
You want to set a cryptographic algorithm policy and stop non-compliant choices from being made in your Amazon Web Services (AWS) environment. This post shows you how. As you adopt post-quantum cryptography, one of the first decisions you face is which algorithms and parameter sets fit your business needs, balancing security against signature size, key…
Protecting sign-ins
- Phishing-resistant multi-factor authentication – passkeys or security keys – for administrators first.
- Block the old sign-in methods that skip MFA, and review who can grant apps access to your data.
- Alert on impossible travel, newly added MFA methods and unusual consent grants.
More helpNCSC: multi-factor authentication for online services (opens in a new tab)
MyCyberWay training
Blue Team Engineer
Build the controls that stop the next one.
Blue Team Engineer: 28 live classes configuring identity, endpoint, email, network and cloud security in your own Azure and Microsoft Defender tenants – then evidencing it against CIS and NIST CSF, and defending every decision. For people with IT, cloud or SOC experience.
- Conditional Access, PIM and tiered admin
- CSPM, Azure Policy and a landing zone
- Detection engineering and SOAR playbooks
Headlines and short summaries only, except where a public body publishes under an open licence. Every story links to its publisher, who owns it. MyCyberWay does not edit or endorse third-party reporting.
