March 2022 Summaries

Operational secrets such as passwords, keys, and certificates must be securely shared among applications, servers, and build systems, but common approaches have limitations: CI/CD-managed secrets can appear in logs, encrypted files require protecting and rotating decryption passwords, and key management services may grant overly broad access while adding infrastructure costs. To address these issues, Basis Theory developed an Ansible Lookup Plugin that stores a Basis Theory token in Ansible configuration and retrieves the underlying secret only when needed during system configuration. Built with the Basis Theory Python SDK and REST API, the plugin uses Ansible’s standard lookup mechanism to fetch a token by ID, allowing playbooks to set variables and populate templates without storing the original secret in configuration or state files.

Robotic Process Automation is expanding rapidly as no-code software bots automate repetitive back-office tasks such as logging into websites, completing forms, processing invoices, and submitting payments, but these workflows often require highly sensitive personal, financial, and authentication data. The text argues that storing such information in plaintext creates major security and compliance risks, making tokenization and encryption essential methods for protecting data between systems. It emphasizes tokenization’s advantage of preserving recognizable data formats, allowing masked values to satisfy website validation rules where encrypted strings may fail. Using no-code RPA platform Weeldi as an example, it describes how customers can use Basis Theory as a third-party token vault, defining sensitive input fields, recording automation templates, and associating those fields with stored tokens rather than retaining raw credentials or card numbers in the RPA platform. During execution, the workflow retrieves plaintext data from the vault only when needed to populate login and payment forms. The piece concludes that organizations evaluating secure RPA infrastructure should seek providers with portability, scalable pricing, granular data-governance controls, and straightforward integrations.

An ASP.NET Core 6 tutorial demonstrates how to build a REST search endpoint that accepts Lucene query syntax, translates it into Entity Framework predicates, and filters an in-memory Persons table. Using a WhitespaceAnalyzer and QueryParser, the endpoint parses requests such as `firstName:Bob OR favoriteFood:Steak`, returning all records when no query is supplied. The implementation converts Lucene query objects recursively into `Expression<Func<Person, bool>>` filters, supporting individual field-value TermQuery predicates, BooleanQuery combinations through AND and OR clauses, and PhraseQuery handling for multi-word values such as favorite foods. Supported searchable fields include first name, last name, social security number, and favorite food, while unsupported query types such as ranges and negation are intentionally excluded. The example also notes that Lucene operators are case-sensitive and cautions that sensitive data should be encrypted in real production systems.