A fault model and mutation testing of access control policies

Evan Martin, Tao Xie

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

To increase confidence in the correctness of specified policies, policy developers can conduct policy testing by supplying typical test inputs (requests) and subsequently checking test outputs (responses) against expected ones. Unfortunately, manual testing is tedious and few tools exist for automated testing of access control policies. We present a fault model for access control policies and a framework to explore it. The framework includes mutation operators used to implement the fault model, mutant generation, equivalent-mutant detection, and mutant-killing determination. This framework allows us to investigate our fault model, evaluate coverage criteria for test generation and selection, and determine a relationship between structural coverage and fault-detection effectiveness. We have implemented the framework and applied it to various policies written in XACML. Our experimental results offer valuable insights into choosing mutation operators in mutation testing and choosing coverage criteria in test generation and selection.

Original languageEnglish (US)
Title of host publication16th International World Wide Web Conference, WWW2007
Pages667-676
Number of pages10
DOIs
StatePublished - 2007
Externally publishedYes
Event16th International World Wide Web Conference, WWW2007 - Banff, AB, Canada
Duration: May 8 2007May 12 2007

Publication series

Name16th International World Wide Web Conference, WWW2007

Other

Other16th International World Wide Web Conference, WWW2007
Country/TerritoryCanada
CityBanff, AB
Period5/8/075/12/07

Keywords

  • Access control policies
  • Fault model
  • Mutation testing
  • Test generation

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Software

Fingerprint

Dive into the research topics of 'A fault model and mutation testing of access control policies'. Together they form a unique fingerprint.

Cite this