490:
74:
176:
33:
361:
In traditional (non-atomic) authorization, policy is defined and secured at an application level. That is, outside the context of the application, there is no mechanism to verify the legitimacy of traditional authorization policy. Atomic authorization requires a
531:
309:
rights independently from the intermediary applications to which they are granted and the parties to which they apply. More formally, in the field of
200:
of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be
91:
46:
524:
392:
lookups, which are protected using single-factor authentication, for authorization information and management. Any application specific
384:) authentication, traditional authorization techniques pose a security vulnerability. The application must rely upon technologies like
455:
289:
271:
157:
60:
252:
138:
555:
550:
224:
110:
373:. Because it is secured independently of the application which use it, atomic authorization policy is equivalent in strength to
517:
95:
231:
117:
197:
238:
124:
193:
220:
209:
106:
52:
333:
that enforces the policy or the individuals who use the application. Resources include access to individual
84:
393:
381:
374:
413:
330:
186:
397:
363:
245:
131:
205:
497:
418:
389:
370:
350:
342:
310:
201:
346:
338:
404:, but does not further legitimize the authorization decisions that the application makes.
448:
501:
428:
423:
326:
322:
544:
367:
306:
17:
73:
489:
401:
385:
329:
of such policy may be independently verified without reliance on the
318:
192:
Please help to demonstrate the notability of the topic by citing
396:
of non-atomic authorization methods increases the complexity of
334:
169:
67:
26:
505:
98:. Unsourced material may be challenged and removed.
525:
8:
61:Learn how and when to remove these messages
532:
518:
290:Learn how and when to remove this message
272:Learn how and when to remove this message
158:Learn how and when to remove this message
439:
325:to a specific resource, such that the
366:to issue authorization policy with a
7:
486:
484:
357:Traditional vs. atomic authorization
96:adding citations to reliable sources
25:
380:For an application using strong (
42:This article has multiple issues.
488:
174:
72:
31:
461:from the original on 2011-06-06
83:needs additional citations for
50:or discuss these issues on the
1:
504:. You can help Knowledge by
187:general notability guideline
454:. George Mason University.
572:
483:
194:reliable secondary sources
183:The topic of this article
185:may not meet Knowledge's
556:Computer security stubs
551:Computer access control
315:to atomically authorize
305:is the act of securing
449:"Atomic Authorization"
447:Dilles, Jacob (2009).
371:guarantee of integrity
221:"Atomic authorization"
107:"Atomic authorization"
375:strong authentication
414:Security engineering
303:Atomic authorization
92:improve this article
18:Atomic Authorization
398:identity management
364:trusted third party
189:
513:
512:
498:computer security
419:Computer security
311:computer security
300:
299:
292:
282:
281:
274:
256:
184:
168:
167:
160:
142:
65:
16:(Redirected from
563:
534:
527:
520:
492:
485:
471:
470:
468:
466:
460:
453:
444:
295:
288:
277:
270:
266:
263:
257:
255:
214:
178:
177:
170:
163:
156:
152:
149:
143:
141:
100:
76:
68:
57:
35:
34:
27:
21:
571:
570:
566:
565:
564:
562:
561:
560:
541:
540:
539:
538:
481:
479:
474:
464:
462:
458:
451:
446:
445:
441:
437:
410:
359:
351:physical access
296:
285:
284:
283:
278:
267:
261:
258:
215:
213:
191:
179:
175:
164:
153:
147:
144:
101:
99:
89:
77:
36:
32:
23:
22:
15:
12:
11:
5:
569:
567:
559:
558:
553:
543:
542:
537:
536:
529:
522:
514:
511:
510:
493:
478:
477:External links
475:
473:
472:
438:
436:
433:
432:
431:
429:Access control
426:
424:Authentication
421:
416:
409:
406:
358:
355:
298:
297:
280:
279:
182:
180:
173:
166:
165:
80:
78:
71:
66:
40:
39:
37:
30:
24:
14:
13:
10:
9:
6:
4:
3:
2:
568:
557:
554:
552:
549:
548:
546:
535:
530:
528:
523:
521:
516:
515:
509:
507:
503:
500:article is a
499:
494:
491:
487:
482:
476:
457:
450:
443:
440:
434:
430:
427:
425:
422:
420:
417:
415:
412:
411:
407:
405:
403:
399:
395:
391:
387:
383:
378:
376:
372:
369:
368:cryptographic
365:
356:
354:
352:
348:
344:
340:
336:
332:
328:
324:
321:that permits
320:
317:is to define
316:
312:
308:
307:authorization
304:
294:
291:
276:
273:
265:
254:
251:
247:
244:
240:
237:
233:
230:
226:
223: –
222:
218:
217:Find sources:
211:
207:
203:
199:
195:
188:
181:
172:
171:
162:
159:
151:
140:
137:
133:
130:
126:
123:
119:
116:
112:
109: –
108:
104:
103:Find sources:
97:
93:
87:
86:
81:This article
79:
75:
70:
69:
64:
62:
55:
54:
49:
48:
43:
38:
29:
28:
19:
506:expanding it
495:
480:
463:. Retrieved
442:
400:and issuing
379:
360:
327:authenticity
314:
302:
301:
286:
268:
262:January 2022
259:
249:
242:
235:
228:
216:
154:
148:January 2022
145:
135:
128:
121:
114:
102:
90:Please help
85:verification
82:
58:
51:
45:
44:Please help
41:
402:credentials
388:queries or
345:, computer
341:, computer
337:, computer
331:application
198:independent
545:Categories
435:References
232:newspapers
206:redirected
118:newspapers
47:improve it
394:hardening
390:directory
196:that are
53:talk page
456:Archived
408:See also
386:database
382:N-factor
377:policy.
347:networks
343:hardware
339:programs
465:16 July
246:scholar
210:deleted
132:scholar
349:, and
323:access
319:policy
248:
241:
234:
227:
219:
202:merged
134:
127:
120:
113:
105:
496:This
459:(PDF)
452:(PDF)
253:JSTOR
239:books
208:, or
139:JSTOR
125:books
502:stub
467:2009
335:data
225:news
111:news
94:by
547::
353:.
313:,
204:,
56:.
533:e
526:t
519:v
508:.
469:.
293:)
287:(
275:)
269:(
264:)
260:(
250:·
243:·
236:·
229:·
212:.
190:.
161:)
155:(
150:)
146:(
136:·
129:·
122:·
115:·
88:.
63:)
59:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
