Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


09:24 AM
Dark Reading
Dark Reading
Products and Releases

Future of Privacy Forum Issues Recommendations For New Presidential Administration

Among seven recommendations, FPF calls for the appointment of a Chief Privacy Officer

WASHINGTON, Jan. 13 /PRNewswire-USNewswire/ -- The Future of Privacy Forum (FPF) today proposed seven privacy recommendations to the upcoming administration. FPF Co-chairs Jules Polonetsky and Christopher Wolf applaud President-Elect Obama for recognizing that the use and development of technology is key to the future of our country. FPF urges the President-elect to also appoint a Chief Privacy Officer (CPO) in order to recognize that responsible use of data by businesses and government is critical to the economy, to protecting civil liberties and to ensuring public safety.

The Future of Privacy Forum recommends the following for the Obama Administration:

1. Appoint a Chief Privacy Officer to Promote Fair Information Practices in the Public and Private Sectors 2. Ensure that Interactive Tools used by Government Provide Users with Enhanced Transparency and Controls 3. Establish a Standard Definition of Personal Information 4. Increase Technology and Research support for the Federal Trade Commission 5. Enhance Criminal Law Enforcement Support for the Federal Trade Commission 6. Provide National Leadership to Resolve the Conflict between Privacy and Online Safety for Youth 7. Encourage Accountable Business Models

"By appointing a CTO, President-Elect Obama will be taking an important and necessary step to ensure that the new Administration has the leadership in place to coordinate technology policies that will improve the quality of life for all Americans," said Wolf. "We are in an era where the personal use of data brings opportunities for advancements that can improve millions of lives, but the misuse of data can also negatively impact millions of citizens."

"As a former CPO I can attest that the partnership between the CTO and CPO is critical for ensuring that new technologies are deployed in a way that respects consumer rights. Traditionally, government privacy protections were intended to limit the collection of data by government about its citizens. In today's web 2.0 environment, citizens expect to interact electronically by exchanging information with government leaders and agencies," said Polonetsky. "Charting the appropriate user controls around this data is critical for both the civic success and the long-term privacy implications of this new relationship."

FPF Board Member Chris Hoofnagle supports the recommendations.

"The Future of Privacy Forum agenda recognizes the link between enhanced consumer protections and trust in online businesses and services," said Hoofnagle, Director of the Berkeley Center for Law & Technology's information privacy programs and senior fellow to the Samuelson Law, Technology & Public Policy Clinic. "Consumer privacy and business priorities are not a zero-sum game; creating sound, reasonable protections for consumers will spread and deepen adoption of internet-based services."

The above proposals do not intend to cover the full range of privacy issues facing the new Administration. Rather, FPF seeks to highlight areas that affect consumers, with co-chairs whose backgrounds give them particular insight into privacy issues. Polonetsky is the former AOL Chief Privacy Officer and Wolf Chairs the Privacy and Data Security Practice Group at Proskauer Rose LLP.

About the Future of Privacy Forum:

The Future of Privacy Forum (FPF) seeks to improve the state of online privacy by advancing responsible data practices. FPF is led by privacy experts Jules Polonetsky and Christopher Wolf and includes an Advisory Board comprised of leading figures from industry, academia, law and advocacy groups. Members of the FPF Advisory Board provide input to the Forum in support of transparency, user control and the advancement of trustworthy data practices. By serving as advisors, they are not responsible for the content of the Web Site nor do they necessarily endorse the positions taken by FPF.

More information on FPF, its mission and Advisory board members can be found online at www.futureofprivacy.org.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...