platform
Our EU Director Dermot Harnett and Deployment Representative Matia Boldrini joined Dublin City University’s Information Systems Services (ISS) Team on April 9, 2024, to discuss the lessons learned and challenges overcome during DCU’s journey to DMARC compliance. The presenters take a straightforward, candid look at the DCU DMARC project, stressing the importance of building relationships and support among university departments and the coworkers that lead them. As you’ll learn in the presentation, DCU ISS was motivated by the NCSC’s email security guidance, and began their DMARC discovery phase, including advocacy among the university leadership and an initial trial with dmarcian. The ISS team shares their challenges for prioritizing this project and how they informed university stakeholders through meetings and internal communications. With the visibility gained through DMARC, they also talk about how they discovered redundant IT resources and were able to gain efficiency. If you weren’t able to join us
What is a PTR Record? A PTR (Pointer) record, also known as a Reverse DNS record, maps an IP address to a domain name; essentially, it’s the opposite of what an A record does in DNS. While A records are used to translate domain names to IP addresses, PTR records are used to verify that an IP address indeed corresponds to a domain name. This is a common verification step for receivers and part of many checks to determine the legitimacy of a connection’s origin, such as email servers. Why Does it Matter? PTR records hold significance for a myriad of reasons across various aspects of internet communication and network management. They facilitate smoother network operations, aid in troubleshooting, and enhance the trustworthiness of servers. However, for the purpose of this article, we will focus on their role in email security and delivery where their impact can be profound. Focusing
Our Single Sign-On (SSO) support leverages Security Assertion Markup Language (SAML) version 2 for Enterprise users. This expedites access to your dmarcian account by letting you sign in with your existing corporate credentials, which means one less password to keep track of. With our SSO, you can easily manage SSO access and user permissions to all of your accounts in dmarcian centrally while adhering to your organization’s security and access policies. Before getting into the details for SSO configuration, let’s first talk about some basic concepts and terminology: Authentication Authentication defines how the user is identified in a system—usually through a login process. Traditionally, a user registers for an account providing authentication credentials (username and password) and uses them to log in moving forward. In the past, this has been sufficient, but it does have limitations. For example, what happens if you have a several employees at your company that you want to grant access
Based on domain events that act as triggers for sending alerts, the highly customizable Alert Central feature on dmarcian’s DMARC Management Platform allows you to monitor your domains without having to login to your dmarcian account. Events could include new or changed DNS records (e.g. we see a new DMARC record) and fluctuation in volume across categories of traffic for your domains. You can choose from common communication channels for alerts—email, Slack, Teams or webhook. The alert will provide you with the details of the event and a link to your dmarcian Timeline for you to get even more information. How does Alert Central Work? Alert Central is based around the dmarcian Timeline. Like the Timeline, you choose which changes to track, and the alerts ensure that you’re aware of the changes in real time. When we notice a DNS change, a change event gets triggered. If a DNS record