GitBAC: Flexible access control for non-modular concerns

  • Authors:

  • Mark Robinson; Jianwei Niu;Macneil Shonle

  • Affiliations:

  • University of Texas at San Antonio, One UTSA Circle, 78249-1644, USA;University of Texas at San Antonio, One UTSA Circle, 78249-1644, USA;University of Texas at San Antonio, One UTSA Circle, 78249-1644, USA

  • Venue:
  • ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

Today's techniques for controlling access to software artifacts are limited to restricting access to whole files and directories. But when a company's access control policy does not match a project's existing physical modularization, these techniques require either an all-or-nothing approach or re-modularization of the files and directories. The increased maintenance overhead this brings to project administration can lead to unimplemented or insufficient developer access control and an increased risk of insider security incidents (e.g., theft of intellectual property). We have created a tool (GitBAC) to provide access control of software artifacts using a crosscutting concern instead of artifact modularization. Our method provides fine-grained access control of artifacts and accommodates flexible access control policies.