Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Tatyana Ryutov

dblp:02/5994 · DBLP profile ↗
← Back
4ranked-venue papers
3as first author
0since 2021 · last 2005
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 3 · 2 first-authorSecurity and privacy · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
2 papers
Authentication and access control · 64% Network security · 28% Web and mobile security · 8%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 50% Cloud and datacenter computing · 50%

Topics — the 8 heaviest of 8, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Authentication and access control
access control
0.012003
Integrated Access Control and Intrusion Detection for Web Servers · IEEE Trans. Parallel Distributed Syst. 2003
Authentication and access control › authorization
dynamic authorization
0.012003
Integrated Access Control and Intrusion Detection for Web Servers · IEEE Trans. Parallel Distributed Syst. 2003
Network security › intrusion detection and prevention
intrusion detection
0.012003
Integrated Access Control and Intrusion Detection for Web Servers · IEEE Trans. Parallel Distributed Syst. 2003
Cloud and datacenter computing › cluster resource management and scheduling
cluster resource management
0.011998
Authorization for Metacomputing Applications · HPDC 1998
Distributed systems › distributed system security
distributed authorization
0.011998
Authorization for Metacomputing Applications · HPDC 1998
Web and mobile security › web security
web server security
0.012003
Integrated Access Control and Intrusion Detection for Web Servers · IEEE Trans. Parallel Distributed Syst. 2003
Authentication and access control
access control models
0.011998
Authorization for Metacomputing Applications · HPDC 1998
Authentication and access control › access control
conditional access
0.011998
Authorization for Metacomputing Applications · HPDC 1998

Methods — techniques the papers use, named apart from their topics

GAA-API · 0.0
YearPublicationVenuePosition
2005 Adaptive trust negotiation and access control
abstract
Electronic transactions regularly occur between business partners in separate security domains. Trust negotiation is an approach that provides an open authentication and access-control environment for such transactions, but it is vulnerable to malicious attacks leading to denial of service or leakage of sensitive information. This paper introduces an Adaptive Trust Negotiation and Access Control (ATNAC) framework to solve these problems. The framework combines two existing systems, TrustBuilder and GAA-API, to create a system with more flexibility and responsiveness to attack than either system currently provides.
Tatyana Ryutov, B. Clifford Neuman, Travis Leithead, Kent E. Seamons
SACMAT1
2003 Integrated Access Control and Intrusion Detection for Web Servers
abstract
Current intrusion detection systems work in isolation front access control for the application the systems aim to protect. The lack of coordination and inter-operation between these components prevents detecting and responding to ongoing attacks in real time, before they cause damage. To address this, we apply dynamic authorization techniques to support fine-grained access control and application level intrusion detection and response capabilities. This paper describes our experience with integration of the Generic Authorization and Access Control API (GAA-API) to provide dynamic intrusion detection and response for the Apache Web Server The GAA-API is a generic interface which may be used to enable such dynamic authorization and intrusion response capabilities for many applications.
Tatyana Ryutov, B. Clifford Neuman
ICDCS1
2003 Integrated Access Control and Intrusion Detection for Web Servers
abstract
Current intrusion detection systems work in isolation from access control for the application the systems aim to protect. The lack of coordination and interoperation between these components prevents detecting and responding to ongoing attacks in real-time before they cause damage. To address this, we apply dynamic authorization techniques to support fine-grained access control and application level intrusion detection and response capabilities. This paper describes our experience with integration of the Generic Authorization and Access Control API (GAA-API) to provide dynamic intrusion detection and response for the Apache Web server. The GAA-API is a generic interface which may be used to enable such dynamic authorization and intrusion response capabilities for many applications.
Tatyana Ryutov, B. Clifford Neuman
IEEE Trans. Parallel Distributed Syst.1
1998 Authorization for Metacomputing Applications
abstract
One of the most difficult problems to be solved by metacomputing systems is to ensure strong authentication and authorization. The problem is complicated since the hosts involved in a metacomputing environment often span multiple administrative domains, each with its own security policy. This paper presents a distributed authorization model used by our resource allocation system, the Prospero resource manager. The main components of our design are extended access control lists (EACLs) and a general authorization and access application programming interface (GAA API). EACLs extend conventional ACLs to allow conditional restrictions on access rights. In the case of the Prospero resource manager, specific restrictions include limits on the computational resources to be consumed and on the characteristics of the applications to be executed by the system, such as name, version or endorser. The GAA API provides a general framework for applications to access the EACLs. We have built a prototype of the system.
Grig Gheorghiu, Tatyana Ryutov, B. Clifford Neuman
HPDC2