[{"pubDate":"Mon, 05 Oct 2026 08:07:08 +0200","id":3197409,"titre":"Stick with Security: Require secure passwords and authentication","description":"Stick with Security: Require secure passwords and authentication lfair August 11, 2017 | 10:47AM Stick with Security: Require secure passwords and authentication By Thomas B. Pahl, Acting Director, FTC Bureau of Consumer Protection To make it harder for hackers to bluff their way onto a computer network, careful companies follow the advice of Start with Security and require strong authentication practices . We’ve considered FTC settlements, closed investigations, and the questions we get from businesses about implementing good authentication “hygiene.” Here are some tips on using effective authentication procedures to help safeguard your network. Insist on long, complex, and unique passwords. A password’s very reason for being is to be easy for a user to remember, but hard for a fraudster to figure out. Obvious choices like ABCABC, 121212, or qwerty are the digital equivalent of a “hack me” sign. Furthermore, experts have determined that passphrases or longer passwords are generally harder to crack. The smarter strategy is for companies to think through their standards, implement minimum requirements, and educate users about how to create stronger passwords. Also, when you install software, applications, or hardware on your network, computers, or devices, change the default password immediately. And if you design products that require consumers to use a password, configure the initial set-up so they have to change the default password. Example: A staff member attempts to select payroll as the password for the database that includes employee payroll information. The company sets up its system to reject an obvious choice like that. Example: To access the corporate network, a business allows employees to type in their username and a shared password common to everyone who works there. Employees are also allowed to use that shared password to access other services on the system, some of which contain sensitive personal information. The more prudent policy would be to require strong, unique passwords for each employee and to insist that they use different passwords to access different applications. Example: At a staff meeting, a company’s IT manager offers tips for employees about good password hygiene. She explains that passphrases or longer passwords are better than short passwords based on standard dictionary words or well-known information (for example, a child’s name, a pet, a birthday, or a favorite sports team). By establishing a more secure corporate password standard and educating employees about implementing it, the IT manager is taking a step to help her company reduce the risk of unauthorized access. Store passwords securely. A company’s first line of defense against data thieves is a workforce trained to keep passwords secret. But even the strongest password is ineffective if an employee writes it on a sticky note on her desk or shares it with someone else. Train your staff not to disclose passwords in response to phone calls or emails, including ones that may appear to be coming from a colleague. Con artists have been known to impersonate corporate officials by spoofing phone numbers or email addresses. A compromised password poses a particular risk if it can be used to open the door to even more sensitive information – for example, a database of other user credentials maintained on the network in plain, readable text. Make it difficult for data thieves to turn a lucky password guess into a catastrophic breach of your company’s most sensitive data by implementing policies and procedures to store credentials securely. Example: A new employee gets a call from someone who claims to be the company’s system administrator. The caller asks him to verify his network password. Because the new staffer learned about impersonation scams at an in-house security orientation, he refuses to disclose his password and instead reports the incident to the appropriate person in the company. Example: A company keeps user credentials and other passwords in plain","url":"https://www.ftc.gov/business-guidance/blog/2017/08/stick-security-require-secure-passwords-authentication","source":"FTC USA Business Blog Posts"},{"source":"Blog d'Arthur Perret","url":"https://www.arthurperret.fr/blog/2023-11-01-document-theory-and-document-design.html","description":"

This paper reports on an experiment which connects document design with document theory. Document design is about what documents should do. We use the example of document graphs and of Cosma, a visualization program created during the HyperOtlet research programme, to show how theory can inform design decisions and help conceptualize results. This paper is currently under peer review.

Document design or information design?

Findeli (2015) defines design as diagnostic and prescriptive, an example of “projective” epistemology: designers view the world as a project to realize, rather than an object to know. This definition of design implies that document design is less about what documents are and more about what they should do. This aligns with the evolution of document theory from an ontic view of documents to a functional one, which was pioneered by the European documentation movement in the first half of the twentieth century and reintroduced as “neo-documentation” in the literature during the 1990s.

Currently in the literature, document design is mostly considered to be a part of information design.1 The purpose of information design is to create effective communications (Renkema 2006 ; see also Pettersson 2002). Document design is usually taught within communications programs ; in the US, in either English or fine arts departments (Schriver 1997, p. 92‑93) ; in France, in Information and Communication Science departments.

Research on information design has very few connections with documentation. It has been criticized for its lack of theory: Carliner (2006, p. 10–14) warned about the field’s tendency to generalize findings despite shaky conceptual foundations and a limited understanding of topics such as the World Wide Web.2 We believe document theory can help address some of these challenges and bring perspective to information design.

Zacklad (2019) gives us an example of this. He draws from document theory to define information design as the interplay between textualization (creating content information), documentarization (shaping the medium) and auctorialization (creating author identities). Zacklad puts documentarization at the heart of information design (see fig. 1). Documentarization can be internal (the organization of fragments into documents) or external (the relational organization of documents, e.g. classification); it can involve different roles or positions (author, editor, printer/programmer, distributor, reader); it implies significant differences between designing the systems that involve documents (“system-oriented design”) and designing the documents themselves (“author design”).