🏠
dev-angelist
HomeGitHubPortfolioTwitter/XMediumCont@ct
  • 🏠Home
  • πŸ“’Certification Notes
    • Certified Ethical Hacker (CEH) Practical
    • CRTP
    • eWPTXv3
    • eCPPTv3
    • eWPTv2
    • eJPTv2
  • ✍️WRITEUPS & WALKTHROUGHS
    • TryHackMe (THM)
    • HackTheBox (HTB)
    • VulnHub
    • DockerLabs.es
    • PortSwigger - Web Sec Academy
    • HomeMade Labs
  • πŸ•ΈοΈWEB
    • eWPTXv3
    • eWPTv2
    • WAPT
    • DVWA
    • Secure Bank
    • Mutillidae II
    • WebSafeHub (WSH)
    • PortSwigger - Web Sec Academy
  • Common Services Pentest
    • Web Services - 80/443/8080
      • Tomcat
        • Lab Setup & Configuration
        • Enumeration
        • Exploitation
        • Mitigation & Hardening
    • SMB - 139/445
  • πŸ‘©β€πŸ’»CODING
    • 🐍Python
      • Python Offensive
      • Email Header Analyzer
      • Dir-Brute
      • Port-Scanner
      • Finger User Enumeration
    • DevSecOps
    • πŸ”ΉPowershell
  • πŸ”΄Offensive Security
    • Active Directory (AD)
      • CRTP
      • AD HomeMade Lab
  • Privilege Escalation
    • Windows Privilege Escalation
  • πŸ”Crypto & AI/ML
    • Crypto & Blockchain
      • Blockchain Security
        • Blockchain Architecture
          • 1.1 Characteristics and Features
          • 1.2 Core Components
          • 1.3 Consensus Algorithm
          • 1.4 Cryptography
          • 1.5 Cryptocurrency
        • Front-end Risks
          • 2.1 MFA and Blockchain
          • 2.2 Front-end
          • 2.3 OWASP Modeling for Blockchain
          • 2.4 Wallet Attacks
          • 2.5 Client Vulnerabilities
        • Back-end Risks
          • 3.1 Consensus Vulnerabilities
          • 3.2 Mining Pool Vulnerabilities
          • 3.3 Network Vulnerabilities
            • 3.3.1 DoS/DDoS/BDoS Attacks
            • 3.3.2 Delay Attacks
            • 3.3.3 Partition Attacks
            • 3.3.4 Sybil Attacks
            • 3.3.5 Time Jacking
            • 3.3.6 Transaction Attacks
        • Mining-Risks
          • 4.1 Mining Overview
          • 4.2 Proof of Stake Post Merge Ethereum
          • 4.3 Crypto Mining Malware (Cryptojacking)
          • 4.4 Zero Trust Models
          • 4.5 Byzantine Fault Tolerance
        • Blockchain as a Service
    • AI/ML Pentest
  • ACTIVE DIRECTORY
    • AD Enumeration
  • Guides & Articles
    • My Articles
    • Guides & Tutorials
      • Burp Suite - Configuration
      • Quickemu - VM
      • Setting Up SSH Keys
      • Building an AD Lab
      • Work Guidelines
  • Windows
    • Windows Enumeration
    • Windows Privilege Escalation
  • INTELLIGENCE GATHERING
    • OSINT
  • LINUX (tbd)
    • Linux Enumeration
    • Linux Privilege Escalation
Powered by GitBook
On this page
  • Authentication
  • Two-Factor Authentication (2FA)
  • MFA and Blockchain Integration
  • Shield Protocol
  1. Crypto & AI/ML
  2. Crypto & Blockchain
  3. Blockchain Security
  4. Front-end Risks

2.1 MFA and Blockchain

PreviousFront-end RisksNext2.2 Front-end

Last updated 6 months ago

Authentication

Authentication is the process of verifying the identity of a user or system before granting access to a resource, service, or application. It is a foundational component of most security systems, ensuring that only authorized users can interact with protected systems.

The standard method of authentication is using combo of Username and Password

Process:

  1. The user enters their username and password.

  2. The system checks the entered credentials against stored data (often stored in a hashed format to ensure security).

  3. If the credentials match, access is granted; otherwise, access is denied.

Security Considerations:

  • Weaknesses: Passwords can be guessed, stolen (phishing attacks), or exposed in data breaches.

  • Improvements: Stronger passwords, password hashing algorithms, and salting techniques can enhance security.

Two-Factor Authentication (2FA)

  • Mechanism: Adds an extra layer of security by requiring the user to present two distinct forms of authentication:

    1. Something the user knows (like a password).

    2. Something the user has (like a phone, hardware token, or an authentication app that generates one-time passcodes).

  • Process:

    1. After entering a password, the user must also provide a code sent via SMS or generated by an authentication app (e.g., Google Authenticator, Authy).

    2. The system checks if the provided second factor matches what is expected before granting access.

  • Security Considerations:

    • Benefits: Reduces the likelihood of unauthorized access because an attacker would need both the password and the second factor (e.g., the user's phone).

    • Weaknesses: 2FA can still be compromised if the second factor is intercepted, for example, through SIM swapping or phishing.

MFA and Blockchain Integration

Blockchain-based MFA systems aim to overcome limitations of traditional MFA by decentralizing authentication data and improving privacy.

1. Decentralized MFA

  • Self-Sovereign Identity (SSI): Users store their identity credentials securely in a blockchain or decentralized storage, eliminating reliance on centralized authentication servers.

  • Smart Contracts: Automate the verification of multiple authentication factors within the blockchain.

2. Blockchain MFA Features

  • Tamper-Proof Authentication Logs: Transactions or login attempts can be recorded on the blockchain for auditability.

  • Tokenized Authentication: Blockchain can issue unique, time-sensitive tokens for MFA.

3. Benefits of Blockchain-Integrated MFA

  • Enhanced privacy: User data is encrypted and decentralized.

  • Improved resilience: No single point of failure.

  • Simplified cross-platform authentication: Works across different applications using the same credentials.

Shield Protocol

Shield Protocol is a blockchain-based security platform that enhances user authentication by integrating decentralized MFA systems. It aims to provide a higher level of security for blockchain and Web3 applications.

Key Features

  1. Decentralized Authentication

    • Shield Protocol eliminates reliance on centralized systems for managing authentication credentials.

  2. 4-Layer Security

    • Provides four layers of authentication for secure access:

      • PIN: A primary access code.

      • Biometric Authentication: Fingerprint or face recognition.

      • Phrase Authentication: Recovery or seed phrases.

      • Blockchain Authentication: Uses decentralized identity or tokens for verification.

  3. Mobile-Based MFA

    • Shield Protocol supports blockchain-based MFA on mobile devices through an app, making it accessible and user-friendly.

  4. Cross-Chain Compatibility

    • Supports multiple blockchains, enabling seamless integration across different platforms and networks.

  5. Key Management

    • Allows users to securely store and retrieve private keys, ensuring a balance between security and convenience.

πŸ”
https://learn.microsoft.com/it-it/entra/identity/authentication/media/tutorial-enable-azure-mfa/conditional-access-overview.png