Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users

Dashboard
Notifications
Mark all as read
Q&A

What makes a software module an "authentication" module?

+0
−2

As I don't have any significant experience with internationally-standard information security literature, I would like to ask here if some international information security organization took the initiative to standardize the terms "authentication" in general and authentication modules in particular as to well define what elements should such a module include in minimum.

What makes a software module an "authentication" module?

I'd guess:

  • Receive a password as input
  • Possibly; receive an email as input
  • Possibly; receive a username as input
  • Possibly; receive an encryption private key as input
  • Possibly; receive a "two factor authentication data"
  • Possibly; receive a Captcha input
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

7 comments

Is "What elements should an authentication module include"? a suitable title (summary) for your post? I think the post's body suggestion such a summary (or similar). Alexei‭ 26 days ago

Have you tried answering this question yourself? Maybe looked up the word ‘authentication’ on Wikipedia? Possibly followed a link from that article to a publication from NIST (not international, but it's not clear why you specifically want an international organization's take—and at any rate, that publication references other ISO standards you could look at)? r~~‭ 26 days ago

On reread, my previous comment maybe comes off like I'm trying to provoke. What I'm trying to do is suggest that you improve this question by sharing more of what you've looked at and why that doesn't satisfy you, or, if you haven't looked at much, by doing that and then coming back with a more specific question. r~~‭ 26 days ago

The purpose of authentication is to establish the identity of the peer, and the number of ways to do that is infinite. Any software that accomplishes that objective can be categorized as authantication software. Your question is therefore ill-formed. But no competently written piece of software is ever going to receive a private key as input. Keys aren't private if they are communicated. EJP‭ 24 days ago

Show 2 more comments

0 answers

Sign up to answer this question »