1
0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-11-18 04:21:34 -05:00
privsec.dev/public/knowledge/index.xml

20 lines
1.3 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Knowledge Base on PrivSec.dev</title>
<link>https://privsec.dev/knowledge/</link>
<description>Recent content in Knowledge Base on PrivSec.dev</description>
<generator>Hugo -- gohugo.io</generator><atom:link href="https://privsec.dev/knowledge/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Multi-factor Authentication</title>
<link>https://privsec.dev/knowledge/multi-factor-authentication/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://privsec.dev/knowledge/multi-factor-authentication/</guid>
<description>Multi-factor authentication is a security mechanism that requires additional verification beyond your username (or email) and password. This usually comes in the form of a one time passcode, a push notification, or plugging in and tapping a hardware security key.
Common protocols Email and SMS MFA Email and SMS MFA are examples of the weaker MFA protocols. Email MFA is not great as whoever controls your email account can typically both reset your password and recieve your MFA verification.</description>
</item>
</channel>
</rss>