The Experts below are selected from a list of 249 Experts worldwide ranked by ideXlab platform

Sandeep S. Kulkarni - One of the best experts on this subject based on the ideXlab platform.

  • Bounded Auditable Restoration of Distributed Systems
    IEEE Transactions on Computers, 2017
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on protocols for Auditable restoration of distributed systems. The need for such protocols arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of In-case-of-emergency-break-glass ). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present two protocols for Auditable restoration, where any process can potentially identify an Auditable Event. The first protocol has an unbounded state space while the second protocol uses bounded state space that does not increase with the length of the computation. In both protocols, whenever a new Auditable Event occurs, the system must reach an Auditable state where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only authorized processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocols are self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, they can be used to provide Auditable restoration to other distributed protocols.

  • Auditable Restoration of Distributed Programs
    arXiv: Distributed Parallel and Cluster Computing, 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and has bounded state space. It can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

  • SRDS - Auditable Restoration of Distributed Programs
    2015 IEEE 34th Symposium on Reliable Distributed Systems (SRDS), 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

Ohio. Department Of Administrative Services. - One of the best experts on this subject based on the ideXlab platform.

  • Other title: DAS-ITS-2100-12-A Auditable Events Standard
    Ohio Department of Administrative Services, 2020
    Co-Authors: Ohio. Department Of Administrative Services.
    Abstract:

    "Effective date: 12/22/2017."; Standard number: DAS-ITS-2100-12-A; "Revision history: 12/22/2017, Original policy; 11/28/2018, Updated the exception request language to align with the current procedure; 02/24/2020, Updated standard template..."--Page 5; Includes bibliographical referencesThe purpose of this standard is to provide requirements to Ohio Department of Administrative Services (DAS) technical teams that will allow for the consistent implementation of Auditable Event standards across information systems. The scope of this standard includes information systems that are developed or acquired by the Ohio Department of Administrative Services (DAS). This standard represents the minimum acceptable criteria governing Auditable Event

  • Other title: DAS-ITS-2100-12-A Auditable Events Standard
    2017
    Co-Authors: Ohio. Department Of Administrative Services.
    Abstract:

    "Original Standard"--Page 4.; "Effective date: 12/22/2017."; Standard number: DAS-ITS-2100-12-A.; Includes bibliographical references.The purpose of this standard is to provide requirements to Ohio Department of Administrative Services (DAS) technical teams that will allow for the consistent implementation of Auditable Event standards across information systems. The scope of this standard includes information systems that are developed or acquired by the Ohio Department of Administrative Services (DAS). This standard represents the minimum acceptable criteria governing Auditable Events

Reza Hajisheykhi - One of the best experts on this subject based on the ideXlab platform.

  • Bounded Auditable Restoration of Distributed Systems
    IEEE Transactions on Computers, 2017
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on protocols for Auditable restoration of distributed systems. The need for such protocols arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of In-case-of-emergency-break-glass ). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present two protocols for Auditable restoration, where any process can potentially identify an Auditable Event. The first protocol has an unbounded state space while the second protocol uses bounded state space that does not increase with the length of the computation. In both protocols, whenever a new Auditable Event occurs, the system must reach an Auditable state where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only authorized processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocols are self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, they can be used to provide Auditable restoration to other distributed protocols.

  • Auditable Restoration of Distributed Programs
    arXiv: Distributed Parallel and Cluster Computing, 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and has bounded state space. It can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

  • SRDS - Auditable Restoration of Distributed Programs
    2015 IEEE 34th Symposium on Reliable Distributed Systems (SRDS), 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

Mohammad Roohitavaf - One of the best experts on this subject based on the ideXlab platform.

  • Bounded Auditable Restoration of Distributed Systems
    IEEE Transactions on Computers, 2017
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on protocols for Auditable restoration of distributed systems. The need for such protocols arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of In-case-of-emergency-break-glass ). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present two protocols for Auditable restoration, where any process can potentially identify an Auditable Event. The first protocol has an unbounded state space while the second protocol uses bounded state space that does not increase with the length of the computation. In both protocols, whenever a new Auditable Event occurs, the system must reach an Auditable state where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only authorized processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocols are self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, they can be used to provide Auditable restoration to other distributed protocols.

  • Auditable Restoration of Distributed Programs
    arXiv: Distributed Parallel and Cluster Computing, 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and has bounded state space. It can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

  • SRDS - Auditable Restoration of Distributed Programs
    2015 IEEE 34th Symposium on Reliable Distributed Systems (SRDS), 2015
    Co-Authors: Reza Hajisheykhi, Mohammad Roohitavaf, Sandeep S. Kulkarni
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.

Kulkarni Sandeep - One of the best experts on this subject based on the ideXlab platform.

  • Auditable Restoration of Distributed Programs
    2015
    Co-Authors: Hajisheykhi Reza, Roohitavaf Mohammad, Kulkarni Sandeep
    Abstract:

    We focus on a protocol for Auditable restoration of distributed systems. The need for such protocol arises due to conflicting requirements (e.g., access to the system should be restricted but emergency access should be provided). One can design such systems with a tamper detection approach (based on the intuition of "break the glass door"). However, in a distributed system, such tampering, which are denoted as Auditable Events, is visible only for a single node. This is unacceptable since the actions they take in these situations can be different than those in the normal mode. Moreover, Eventually, the Auditable Event needs to be cleared so that system resumes the normal operation. With this motivation, in this paper, we present a protocol for Auditable restoration, where any process can potentially identify an Auditable Event. Whenever a new Auditable Event occurs, the system must reach an "Auditable state" where every process is aware of the Auditable Event. Only after the system reaches an Auditable state, it can begin the operation of restoration. Although any process can observe an Auditable Event, we require that only "authorized" processes can begin the task of restoration. Moreover, these processes can begin the restoration only when the system is in an Auditable state. Our protocol is self-stabilizing and has bounded state space. It can effectively handle the case where faults or Auditable Events occur during the restoration protocol. Moreover, it can be used to provide Auditable restoration to other distributed protocol.Comment: 10 page