2019
DOI: 10.6028/nist.sp.800-205-draft
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Attribute Considerations for Access Control Systems

Abstract: This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercis… Show more

Help me understand this report
View published versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0
1

Year Published

2021
2021
2022
2022

Publication Types

Select...
3

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 6 publications
(7 reference statements)
0
3
0
1
Order By: Relevance
“…We consider the number of attributes to be finite for the complexity of the algorithm to be bounded. In addition, for different purposes, we may need multiple tables in the database such as one for EDR recording keeping with a limited pool of a week of log record, another for compressed and reduced data set for prolonged storage and future analysis, and one additional table for access control [8], [10], [11] and credentials. Our database system would be having the flexibility to add or remove tables, attributes and perform database normalization [17] as per requirements.…”
Section: Database Architecture For Edr Summarymentioning
confidence: 99%
See 1 more Smart Citation
“…We consider the number of attributes to be finite for the complexity of the algorithm to be bounded. In addition, for different purposes, we may need multiple tables in the database such as one for EDR recording keeping with a limited pool of a week of log record, another for compressed and reduced data set for prolonged storage and future analysis, and one additional table for access control [8], [10], [11] and credentials. Our database system would be having the flexibility to add or remove tables, attributes and perform database normalization [17] as per requirements.…”
Section: Database Architecture For Edr Summarymentioning
confidence: 99%
“…Attributes periodically collected using EDR tools may vary as per their weight in the function of a trust score and its trustworthiness [2], based on which access to a resource is granted. A trust score function can also vary from network to network and can be altered as per requirements as some weak attributes for an enterprise can be strong attributes for another [8].…”
Section: Introductionmentioning
confidence: 99%
“…Utilizar uma cache para essas identidades é uma forma de atender esse requisito. Além de que outros benefícios como ter disponível as identidades quando os repositórios originais não podem ser acessados por questões de emergências como baixa largura de banda ou perda de servic ¸o [Hu et al 2019]. A partir da cache de identidades é possível recuperar dados diretamente, sem a necessidade de consultar o diretório de origem do usuário.…”
Section: Cacheunclassified
“…To ensure AC data security, functions to satisfy the following three security requirements may also need to be included [SP205]:…”
Section: Systemsmentioning
confidence: 99%