skip to main content
tutorial

Gem #82: type-based security 1: handling tainted data

Published:22 February 2012Publication History
Skip Abstract Section

Abstract

Ada Gem #82 --- The strong type system in Ada makes it quite convenient to check at compile time that certain security properties are verified, for example that a tainted value is not used where a trusted one is expected, or that data is properly validated before being used in a sensitive context (think of SQL injection attacks). In this series of two Gems, we present short examples of how this might be done. The first Gem discusses how to handle tainted data.

Recommendations

Comments

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Sign in

Full Access

  • Published in

    cover image ACM SIGAda Ada Letters
    ACM SIGAda Ada Letters  Volume 31, Issue 2
    August 2011
    62 pages
    ISSN:1094-3641
    DOI:10.1145/2148436
    Issue’s Table of Contents

    Copyright © 2012 Copyright is held by the owner/author(s)

    Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    • Published: 22 February 2012

    Check for updates

    Qualifiers

    • tutorial
  • Article Metrics

    • Downloads (Last 12 months)0
    • Downloads (Last 6 weeks)0

    Other Metrics

PDF Format

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader