Results 1 - 10 of 71

Intellectual Property Rights Requirements for Heterogeneously-Licensed Systems

by Thomas A. Alspaugh, Hazeline U. Asuncion, Walt Scacchi
"... Heterogeneously-licensed systems pose new challenges to analysts and system architects. Appropriate intellectual property rights must be available for the installed system, but without unnecessarily restricting other requirements, the system architecture, and the choice of components both initially ..."
Abstract - Cited by 27 (19 self) - Add to MetaCart
Heterogeneously-licensed systems pose new challenges to analysts and system architects. Appropriate intellectual property rights must be available for the installed system, but without unnecessarily restricting other requirements, the system architecture, and the choice of components both initially and as it evolves. Such systems are increasingly common and important in e-business, game development, and other domains. Our semantic parameterization analysis of open-source licenses confirms that while most licenses present few roadblocks, reciprocal licenses such as the GNU General Public License produce knotty constraints that cannot be effectively managed without analysis of the system’s license architecture. Our automated tool supports intellectual property requirements management and license architecture evolution. We validate our approach on an existing heterogeneously-licensed system. 1.
(Show Context)

A Privacy in mobile technology for personal healthcare

by Sasikanth Avancha, Amit Baxi, DAVID KOTZ
"... Information technology can improve the quality, efficiency, and cost of healthcare. In this survey, we examine the privacy requirements of mobile computing technologies that have the potential to transform healthcare. Such mHealth technology enables physicians to remotely monitor patients’ health, a ..."
Abstract - Cited by 25 (6 self) - Add to MetaCart
Information technology can improve the quality, efficiency, and cost of healthcare. In this survey, we examine the privacy requirements of mobile computing technologies that have the potential to transform healthcare. Such mHealth technology enables physicians to remotely monitor patients’ health, and enables individuals to manage their own health more easily. Despite these advantages, privacy is essential for any personal monitoring technology. Through an extensive survey of the literature, we develop a conceptual privacy framework for mHealth, itemize the privacy properties needed in mHealth systems, and discuss the technologies that could support privacy-sensitive mHealth systems. We end with a list of open research questions.

Experiences in the Logical Specification of the HIPAA and GLBA Privacy Laws

by Henry Deyoung, Dilsun Kaynar, Deepak Garg, Anupam Datta, Limin Jia
"... Despite the wide array of frameworks proposed for the formal specification and analysis of privacy laws, there has been comparatively little work on expressing large fragments of actual privacy laws in these frameworks. We attempt to bridge this gap by giving complete logical formalizations of the t ..."
Abstract - Cited by 17 (4 self) - Add to MetaCart
Despite the wide array of frameworks proposed for the formal specification and analysis of privacy laws, there has been comparatively little work on expressing large fragments of actual privacy laws in these frameworks. We attempt to bridge this gap by giving complete logical formalizations of the transmission-related portions of the Health Insurance Portability and Accountability Act (HIPAA) and the Gramm-Leach-Bliley Act (GLBA). To this end, we develop the PrivacyLFP logic, whose features include support for disclosure purposes, real-time constructs, and self-reference via fixed points. To illustrate these features and demonstrate PrivacyLFP’s utility, we present formalizations of a collection of clauses from these laws. Due to their size, our full formalizations of HIPAA and GLBA appear in a companion technical report. We discuss ambiguities in the laws that our formalizations revealed and sketch preliminary ideas for computer-assisted enforcement of such privacy policies.
(Show Context)

Automated Privacy Audits Based on Pruning of Log Data

by Rafael Accorsi, Thomas Stocker
"... This paper presents a novel approach to automated audits based on the pruning of log data represented as trees. Events, recorded as a sequential list of entries, are interpreted as nodes of a tree. The audit consists in removing the nodes that are compliant with the policy, so that the remaining tre ..."
Abstract - Cited by 16 (14 self) - Add to MetaCart
This paper presents a novel approach to automated audits based on the pruning of log data represented as trees. Events, recorded as a sequential list of entries, are interpreted as nodes of a tree. The audit consists in removing the nodes that are compliant with the policy, so that the remaining tree consists only of the violations of the policy. Besides presenting the method, this paper demonstrates that the resultant method is more efficient than usual audit approaches by analyzing its theoretical complexity and the runtime figures obtained by a proof of concept. 1.
(Show Context)

Security Requirements Engineering via Commitments

by Fabiano Dalpiaz, Elda Paja, Paolo Giorgini
"... with the elicitation of security needs and the specification of security requirements of the system-to-be. Current approaches to SRE either express stakeholders ’ needs via highlevel organisational abstractions that are hard to map to system design, or specify only technical security requirements. I ..."
Abstract - Cited by 16 (14 self) - Add to MetaCart
with the elicitation of security needs and the specification of security requirements of the system-to-be. Current approaches to SRE either express stakeholders ’ needs via highlevel organisational abstractions that are hard to map to system design, or specify only technical security requirements. In this paper, we introduce SecCo, an SRE framework that starts with goal-oriented modelling of the security needs and derives security requirements from such needs. Importantly, SecCo relates security requirements to the interaction among actors. Security requirements are specified as social commitments— promises with contractual validity from one actor to another— that define constraints on the way actors can interact. These commitments shall be implemented by the system-to-be. Index Terms—Security requirements; Goal models; Commitments I.
(Show Context)

Legal requirements, compliance and practice: an industry case study

by Travis D. Breaux, Annie I. Antón - in accessibility.” IEEE 16th Int’l Req’ts Engr. Conf , 2008
"... U.S. laws and regulations are designed to support broad societal goals, such as accessibility, privacy and safety. To demonstrate that a product complies with these goals, businesses need to identify and refine legal requirements into product requirements and integrate the product requirements into ..."
Abstract - Cited by 14 (8 self) - Add to MetaCart
U.S. laws and regulations are designed to support broad societal goals, such as accessibility, privacy and safety. To demonstrate that a product complies with these goals, businesses need to identify and refine legal requirements into product requirements and integrate the product requirements into their ongoing product design and testing processes. We report on an industry case study in which product requirements were specified to comply with Section 508 of the U.S. Workforce Investment Act (WIA) of 1998. This study sought to identify: limitations in existing requirementsacquisition methods; compliance gaps between previously specified product requirements and Section 508 of the WIA; and additional sources of knowledge that are necessary to refine legal requirements into product requirements to comply with the law. Our study reveals the need for a community of practice and generalizable techniques that can reduce ambiguity, complexity and redundancy in legal and product requirements and manage innovation in product requirements. We present these findings with several examples from Section 508 regulations and actual product requirements that are implemented in Cisco products. 1.
(Show Context)

Detective information flow analysis for business processes

by Rafael Accorsi, Claus Wonnemann - in Business Processes, Services Computing and Intelligent Service Management, ser. LNI
"... Abstract: We report on ongoing work towards a posteriori detection of illegal information flows for business processes, focusing on the challenges involved in doing so. Resembling a forensic investigation, our approach aims at analyzing the audit trails resultant from the execution of the business p ..."
Abstract - Cited by 12 (10 self) - Add to MetaCart
Abstract: We report on ongoing work towards a posteriori detection of illegal information flows for business processes, focusing on the challenges involved in doing so. Resembling a forensic investigation, our approach aims at analyzing the audit trails resultant from the execution of the business processes, locating informations flows that violate the (non-functional) requirements stipulated by security policies. The goal is to obtain fine-grained evidence of policy compliance with respect to information flows. Information flow (IF) characterizes the transfer of information from a classified container h to a public container l during the execution of a process [Lam73]. A “container ” can be a logical or physical device, such as a process instance, network socket, or variable. An IF is labeled “illegal ” whenever it violates the security policies expressing the non-functional requirements put on the execution of the process, in particular the confidentiality and noninterferability of pieces of information. Asserting that the executions of business processes do not allow illegal IF is essential in the context of regulatory compliance [KGM08], which is largely automated by business processes deployed over service-oriented architectures [AMK02]. Most of the compliance

Automating the Extraction of Rights and Obligations for Regulatory Compliance

by Nadzeya Kiyavitskaya, Nicola Zeni, Travis D. Breaux, Annie I. Antón, James R. Cordy, Luisa Mich, John Mylopoulos
"... Abstract. Government regulations are increasingly affecting the security, privacy and governance of information systems in the United States, Europe and elsewhere. Consequently, companies and software developers are required to ensure that their software systems comply with relevant regulations, eit ..."
Abstract - Cited by 12 (5 self) - Add to MetaCart
Abstract. Government regulations are increasingly affecting the security, privacy and governance of information systems in the United States, Europe and elsewhere. Consequently, companies and software developers are required to ensure that their software systems comply with relevant regulations, either through design or re-engineering. We previously proposed a methodology for extracting stakeholder requirements, called rights and obligations, from regulations. In this paper, we examine the challenges to developing tool support for this methodology using the Cerno framework for textual semantic annotation. We present the results from two empirical evaluations of a tool called “Gaius T ” that is implemented using the Cerno framework and that extracts a conceptual model from regulatory texts. The evaluation, carried out on the U.S. HIPAA Privacy Rule and the Italian accessibility law, measures the quality of the produced models and the tool’s effectiveness in reducing the human effort to derive requirements from regulations. 1
(Show Context)

InDico: Information flow analysis of business processes for confidentiality

by Rafael Accorsi, Claus Wonnemann - ERCIM Workshop on Security and Trust Management, volume 6710 of Lecture Notes in Computer Science , 2011
"... Abstract. This paper presents InDico, an approach for the automated analysis of business processes against confidentiality requirements. InDico is motivated by the fact that in spite of the correct deployment of access control mechanisms, information leaks in automated business processes can persist ..."
Abstract - Cited by 10 (6 self) - Add to MetaCart
Abstract. This paper presents InDico, an approach for the automated analysis of business processes against confidentiality requirements. InDico is motivated by the fact that in spite of the correct deployment of access control mechanisms, information leaks in automated business processes can persist due to erroneous process design. InDico employs a meta-model based on Petri nets to formalize and analyze business processes, thereby enabling the identification of leaks caused by a flawed process design.
(Show Context)

Formalizing and Enforcing Purpose Restrictions in Privacy Policies (Full Version)

by Michael Carl, Tschantz Anupam Datta, Jeannette M. Wing , 2012
"... views and conclusions contained in this document are those of the authors and should not be interpreted as ..."
Abstract - Cited by 8 (6 self) - Add to MetaCart
views and conclusions contained in this document are those of the authors and should not be interpreted as