Test Security Incidents “Test security incidents are behaviors prohibited during test administration, either because they give a student an unfair advantage or because they compromise the secure administration of the assessment.” “Whether intentional or by accident, failure to comply with security rules, either by staff or students, constitutes a security incident.” Three levels of incidents are reported according to level of severity of incident: 1

1.IMPROPRIETY: Low level of severity  Low risk of potentially affecting student performance on test, test security, or validity  EXAMPLES: Students talking during test; student leaves test room without supervision  REPORTING: Correct problem at school; may report to McCaslin by for local log. 2.IRREGULARITY: Medium level of severity  Higher risk of affecting student performance, test security, or validity  EXAMPLES: Student cheating, helping others, using cell phone or internet; fire drill, lockdown, power outage; Proctor coaching, leading students, assisting in responses  REPORTING: Correct problem at school; report to McCaslin. If need to restart tests immediately or reopen a test that was submitted in error, school logs request for resolution in the TIDE Appeals system. McCaslin contacts SDE. 3.BREACH: High level of severity  Significant threat to the validity of the test.  EXAMPLE: Copying, photographing, removing test stimuli or items; using test information for instructional purposes; release of secure materials  REPORTING: Report to McCaslin IMMEDIATELY/phones in report to SDE 2 3 Levels of Incident Severity/Reporting

Appeals Invalidate test: eliminates that test (e.g, cheating) Reset test: removes test, student can start a new test (e.g., wrong accommodations) Re-open test: after submitted in error Restore test: return to previous test after reset in error 3