NSF award 2451803 · Portland State University

CRII: SaTC: Preventing inferences in databases through Dependency-Aware Access Control

Final report due

28 January 2028

in 467 days · The award ends on 30 September 2027.

GrantClerk is a private service. We are not NSF or any government agency.

Dates this award owes

NSF emails you about this too.

Decide about an extension2 Jun 2027in 227 days
award ending 2027-09-30 · Research.gov
This one is ours, not NSF’s.
Extension request16 Aug 2027in 302 days
award ending 2027-09-30 · Research.gov
PAPPG 24-1: “at least 45 days prior to the end date”
No-cost extension notice20 Sep 2027in 337 days
award ending 2027-09-30 · Research.gov
PAPPG 24-1: “at least ten calendar days prior to the end date”
Final report due28 Jan 2028in 467 days
award ending 2027-09-30 · Research.gov
PAPPG 24-1: “no later than 120-days following the end date of the award”
Project outcomes report due28 Jan 2028in 467 days
award ending 2027-09-30 · Research.gov
PAPPG 24-1: “no later than 120 days following the end date”
Award is closed out28 Jan 2028in 467 days
award ending 2027-09-30 · Research.gov
PAPPG 24-1: “financially closed out 120 days after their expiration date”

Annual report dates come from the budget period on your award notice. That date is not public, so it is not shown here.

How we got this date

NSF lists this award's end date as 30 September 2027.
NSF rules say the final report is due no later than 120 days after that.
So the final report is due by 28 January 2028.

Read the rule on Research.gov

Get a note before each report date

Add this award to your desk. We email you before each date and keep the dates in one place.

Renews each year until you cancel. Cancel any time from your account.

Already a member? Sign in

Award card

Award number: 2451803
Period of support: 1 Oct 2025 – 30 Sep 2027
Amount: $174,991
Awardee: Portland State University, Portland, OR
Program: Secure &Trustworthy Cyberspace
Directorate: CSE

Abstract

Fine-grained access control policies define what data is sensitive or non-sensitive in a database. While these policies guard against direct access to sensitive data, attackers can still make guesses (or inferences) about sensitive data using non-sensitive data and data dependencies. Data dependencies, or simply dependencies, specify relationships between items within a database. For example, in an employee…

Is this right?

We copy this from the public NSF award record. Your award notice and NSF always win. If a date looks wrong, check Research.gov.